|
/free syntax checking in SEU is essentially non-existent in v5r2. I'm not sure the syntax checker has *ever* flagged anything within a /free - /end-free block. And, believe me, I had all kinds of newbie syntax errors early on, but had to rely on a compile listing *ERR scan to find them.
Have you found it to be better in WDSC? I haven't.In my experience, /FREE statements are pretty much always EVAL or CALLP statements. Fixed-format statements don't validity check the "extended factor 2" portion of those statements, either. The only real advantage as far as validity checking goes is when you're using other opcodes besides EVAL and CALLP... that's why it's "slightly better" for fixed format stuff vs. free format stuff... because it's better for those opcodes besides EVAL and CALLP, which make only a small percentage of my programs.
Not intending to beat *this* dead horse again, but, dang, if we could just get rid of the statement-ending semicolons!
We're not talking about how the language shoudl've been designed (in this thread) This discussion is about the pros and cons of fixed vs. free. Can we please not go off on the tangent of telling IBM how to design a language that's already been designed and is already in production where it can't be changed? Thanks.
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.
midrange.com
