RE: Prototyped Procedures

Right, that's the bad manners I was referring to.
Valid? From what I know, anything that compiles and works is "valid".
Just because you can do something, makes it valid.
Just because you can do something, doesn't mean it is a good solution.
I just spent hours and hours pulling out hard-coded library names from CL
because the previous programmers thought using TSTDATA for a library name
and then hard coding it (i.e., qualifying) to files all over the plays was
"valid". 
Sometimes you've got to remember what Crocodile Dundee said, and I
paraphrase: "Sure you can do it, but it tastes like shit."

I take this to mean, sure some things will solve of short-term problem, but
if you're not too lazy you can find a broad-base solution. 
-Bob



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Joe Pluta
Sent: Tuesday, February 01, 2005 10:06 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Prototyped Procedures

> From: Bob Cozzi
> 
> The best thing to do is to put the prototypes someplace other than
within
> the procedure implementation source. Keeping it altogether in one
source
> member is just bad manners.  :)

And then there are those of us who use the /DEFINE method to keep the
prototype in the module source.  That way, we have only one source file
to modify.  It's just as valid an approach as any.

Joe

-- 
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.