|
If you need /free and /end-free tags "all over the place" then you couldn't use this all source alternative anyway, could you? But if your code does fall into this criteria, then you'd just have to use one /free and one /end and that doesn't seem like too much coding. Or am I missing something? -----Original Message----- From: John Taylor [mailto:lists@xxxxxxxxxxxxxxxxxxxx] Sent: Wednesday, July 09, 2003 1:01 PM To: rpg400-l@xxxxxxxxxxxx Subject: Free form code suggestion Hans/Barbara, Would it be feasible to introduce a control specification keyword to indicate that ALL source statements within a given member (and/or /copy'd in) are free-form statements? The idea would be to eliminate the requirement for /FREE and /END-FREE tags all over the place. Regards, John Taylor
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.