I just bought PBCC ver 6 and it will be worth it even for a 10% speed improvement. Thanks to everyone. I now have to convert 8000 lines of code (much of it badly written) so I may not survive the process. I have made a start and now is a good time to consider the program structure. Given the interest in speed, is there any program structure to avoid/use? Writing to the screen (minimising of) has been mentioned in this thread but I guess there are other traps.
Someone, who knows more about this than I do, said in a corporate environment you plan out the structure for months and then writing the code is simple as you already know what to do. This is a really weird concept for me. I expect there is a procedure/framework to use when planning. Is there a reference somewhere that provides examples? My program is quite simple and the problem may be the corporate models are too big/complex to follow.
Someone, who knows more about this than I do, said in a corporate environment you plan out the structure for months and then writing the code is simple as you already know what to do. This is a really weird concept for me. I expect there is a procedure/framework to use when planning. Is there a reference somewhere that provides examples? My program is quite simple and the problem may be the corporate models are too big/complex to follow.
Comment