|
I guess I didn't state what I trying to say to well. When I say a subroutine, I generally mean a routine that is passed parameters and returns parameters. Such as in C, Pascal, etc... When talking about non RPG specific things, such as Static variables, I sometimes fall into the habit of calling these subroutines instead of the RPG term, subprocedures. For everything that was discussed here, an RPG subroutine (BegSR... EndSR) could be considered to be inline to the main body of the program. It's sometimes gotten my ire up that IBM has renamed a lot of the industry standard terms, Subroutines -> Subprocedures, Directory -> Library, Library -> Directory, etc.. although that was not intended by IBM, it just happened by the way the AS/400 matured. They had parts of code you could call called Subroutines, just as Basic did in the early days (GOSUB) but in basic they were usually called "Gosubs". Then when Basic followed C and had callable Functions and Subroutines they called them that, Functions and Subroutines. IBM already had something called Subroutines so they needed a new name to avoid confusion, hence the term Subprocedure was born. Fine and dandy if all you talk about is IBM AS/400s, but when you start talking about programming in general it gets confusing to me, which is why I sometimes refer to AS/400's subprocedures as subroutines. Regards, Jim Langston Me transmitte sursum, Caledoni! Joep Beckeringh wrote: > > > And, yes, to me Subprocedure and Subroutine are synonyms. > > Hm. How would you call a subroutine within a subprocedure? (Yes, that IS > possible). > > Joep Beckeringh +--- | 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.