|
Bob Cozzi wrote: > > > If you really need to use #, perhaps we should require that all opcode names > begin with @ and all field names begin with # that way procedure names could > begin with any other symbol, and built-in functions would begin with %. > Hans would be able to write the CF-spec stuff parser even faster. Hey, why > not just port the Spreadsheet language (ala VisiCalc) to the AA/400 and call > it RPG IV with CF-specs. :) > Talking about variable names, can we drop that silly requirement that variable has to start with A-Z,$,#,@ and allow numbers in the first position of the field name? Also special characters in field names? I get the feeling the compiler checks the first character in the field name to fix it as a field? -- Thank You. Regards Dave Mahadevan.. mailto:mahadevan@fuse.net +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---END
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.