|
If I need the internal procedure array to be static, would I still get better performance by passing the array in as param? See below:
The memory of a (by-reference) parameter isn't allocated by the subprocedure that receives the parms. So, declaring it static wouldn't make sense.
Also, you can eliminate the need for pointer logic by making myScreen a data structure, and making prScreenAry a subfield of that data structure.
Also, I don't think VT100 screens are fixed at 80 x 24. I think you can change the number of rows and columns at will. I suppose the original VT100 dumb terminals probably had fixed columns & rows, but nowadays, people who use VT100 emulation are almost always using a PC program of some sort, and they can all change the number of columns and rows by dragging the window edge. (Just something to think about.)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
