Re: Benefits of Sub-procedures

[G Armour <garmour400r@xxxxxxxxx>]

--- Barbara Morris <bmorris@xxxxxxxxxx> wrote:
> Andy Holmer wrote:
> > Barbara,
> > 
> > Please correct me if I misunderstand this...
> > >
> > I can always prototype the program call incorrectly.  The compiler will
> > ensure that I call the way that I have prototyped, but not necessarily
> > the way the *Entry PLIST was defined.  I do not get that kind of
> > checking unless I use Sub-Procedures and a /COPY book to check the
> > prototype against the interface as I compile the module.
> 
> Andy, you can write your program to /copy in the prototype and use a
> procedure interface instead of the *ENTRY PLIST.  Then you get the same
> parameter checking as with procedures.

<After blank gaze passes>
This love affair with /copy baffles me.  But if this is an advantage for 
prototypes,
why not just /COPY the parameters for the *ENTRY & CALL PLISTs?  If you do that,
what advantage do prototypes have over *ENTRY?

Not picking a fight, just really curious.  Honest.

GA


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com