|
>>> Do you think the D- and F- specs should be free-format? What advantage would this provide? The funny thing is that everyone would line up their definitions anyway <grin> Of course it would make it easier to code long procedure names etc. but personally I'm not sure the money spent on it would be a worthwhile investment. 99% of what bugs me would be dealt with by simply having the compiler recognize that if cols 6 and 7 are blank - then it is free form. No /Free and no annoying /End-Free at the end of the main line and every subprocedure. It is not the fixed form D and F that really annoy me - it is the in-an-out of /Free. Jon Paris Partner400 www.Partner400.com
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.