|
Hans or Barbara may be able to answer this for me... Are there any plans on allowing F and O specs inside of Subprocedures? I know that F and O specs are currently source file wide, we can put them at the top above the subprocedures either in programs or in modules (well, not positive on O specs in modules, never tried that but I assume it would work). I sometimes think it would make for better coding to be able to have an F spec and/or O spec for a subprocedure that isn't utilized in the rest of the source file. I guess because when I'm working on a subprocedure for a program and I need to check how a file is opened or such I don't like having to go all the way to the top of my 3350 line program, look at the F spec, they try to find out where my subprocedure was again. No, I can not think of any legitimate logical reason for wanting to be able to code them local to a procedure, I don't see it giving me one iota of additional capability. It's just something I think would be nice. And I wouldn't mind at all if we were limited to UsrOpn and Except processing for these. Regards, Jim Langston Me transmitte sursum, Caledoni! +--- | 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 +---
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.