Re: No Subroutines (was Re: Debugging many subprocedures)

I have heard there is improvements in V5R4. Remeber, this is a hearsay. I 
don't know anything for sure.

On 7/27/05, Alan Campin <Alan.Campin@xxxxxxx> wrote:
> 
> Like I said, unless you have to. SQL not being free(IBM, why, why why) is 
> one place where I still use them. I used subroutines for screen programs 
> until recently and converted to subprocedures but even then, I used them 
> inside a subprocedure. Works very nicely. Having local variable for things 
> like LoadOnePage makes things a lot clear and simpler. See my Trigger 
> Mediator TG0002 for examples.
> 
> Also, opinion, I think freeing SQL in RPG/ILE is so important IBM ought to 
> do it and put it into the SQL pre-compiler as a PTF. Anybody else think so? 
> The only thing that is effected is the SQL pre-compiler and not much of 
> that. Why is IBM making it such a big deal?
> 
> >> -----Original Message-----
> >> From: Joe Pluta [mailto:joepluta@xxxxxxxxxxxxxxxxx]
> >> Sent: Wednesday, July 27, 2005 10:52 AM
> >> To: 'RPG programming on the AS400 / iSeries'
> >> Subject: RE: No Subroutines (was Re: Debugging many subprocedures)
> 
> 
> >> The opinions of my esteemed colleagues' Mssrs. Gibbs and Campin
> >> notwithstanding, I think "no subroutines" is a little bit of overkill.
> >> Subroutines are quite useful for segmenting code where the code is
> >> already using global constructs. For example, I find it quite nice for
> >> separating the various routines of a UI program; I have one subroutine
> >> for each page, and one subroutine for each function in the page. I then
> >> cycle through the subroutines using state variables. Since the pages
> >> all access the screen fields and they themselves are by definition
> >> global, little is gained by turning these subroutines into procedures.
> 
> >> Another place where subroutines come in handy is in the segmenting of
> >> non-free-form opcodes, especially embedded SQL. In order to avoid the
> >> ugliness of /free and /end-free, I can put my SQL code into subroutines
> >> and then invoke them from business logic written in /free.
> 
> >> I just don't agree with the blanket assertion that subroutines are
> >> always bad. Every block of code doesn't necessarily need the
> >> syntactical overhead of a procedure and the associated prototype.
> 
> >> Joe
> 
> 
> > From: Mike Wills
> >
> > Really? That is a good thing? Why is that?
> >
> > On 7/27/05, David Gibbs <david@xxxxxxxxxxxx> wrote:
> > >
> > > Mike Wills wrote:
> > > > I my vendor's infinite wisdom, there is not subroutines in their
> code,
> > > it is
> > > > all subprocedures.
> > >
> > > In that respect, they are truly wise. Seriously.
> 
> 
> 
> 
> 
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
> 
>