|
It just seems to me that taking advantage of what's already included in the language would be better to expand on. For example, on the ExtFile keyword, perhaps allow multiple parameters, ex. ExtFile('lib/filename':'lib/filename') where the second paramenter (which could never be a variable) would point to the file to use during the compile. Perhaps even include a parm for the system name that contains the file. In this way, you aren't really adding another layer to the whole mess, with CL commands (never mind what happens when the CL commands change -- what about positional parameters, etc??? -- that's scary, if you ask me). I agree that if you are going to start embedding commands in your program for the compiler, this really is going too far. -- "Enter any 11-digit prime number to continue..."
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.