|
Hans, >is there a single easy thing we could do to improve the >language? Switch to a completely free-form syntax (or at least the calcs), so we can start our expressions closer to the left-hand side then indent for readability. :) Seriously, as far as I'm concerned, it would be good enough to implement it similar to how Paul Conte's RPG/free did, so even existing opcodes with factor 1/2 or result field, etc requirements would not necessarily need major rework. It wouldn't even bother me significantly if the operands in those cases were limited to the size constraints of the current (ILE) fixed-format columns. Just add a phase effective between /FREE and /FIXED pairs (or whatever) where the source lines get reformatted then passed to the existing parsing routintes. Now that we can code our own subprocedures (the single biggest improvement in my book!), RPG has in essence become extensible. With completely free-format, indentable calcs, RPG would be a great language. IMHO, Doug +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.