RE: Prototyped Procedures

Bob,

This type of pretentious dogma and personal assaults are precisely why I avoid 
these types of discussions.

<snip>
I think you answered your own question:
>> As a longtime no /copy bigot
</snip>
You conveniently omitted the remainder of the sentence.  In its entirety it 
read 'As a longtime no /copy bigot I'm still coming to terms with using /copy 
(or /include) for prototypes.'  This was intended to communicate my background 
and willingness to change and try new methods of coding.

<snip>
To me, though, it is confusing and gimmicky to use this "technique".
</snip>
Your opinion, and why I asked the question.  I wish you had spent more time on 
explaining why and less time guessing at what tools I use to edit code.

<snip>
If I did that with RPG xTools, I would have had to have shipped everyone the
entire source library rather than just the prototypes.
</snip>
Believe it or not, this does make some sense.  If I was selling a package I 
wouldn't want to send the entire source library to all my customers.  There 
are, however, vendors that do sell source code and expect their customers to 
customize it.  We aren't a software vendor so that isn't an issue.

<snip>
I'm guessing you're using SEU to edit your code... this all-in-one-source
mentality runs rapid in SEU users.
</snip>
No, actually I have been using WDSc exclusively for the last two years and have 
been at the forefront of getting it adopted in our shop.  Not that it has any 
bearing on this thread.  As I don't recall seeing any posts from you on the 
WDSc list I could presume that you are still using SEU.  But then, it's really 
none of my business and doesn't matter anyway for the purpose of the discussion 
I was trying to have.

I'm sure you don't remember, but I met you once in 1995 at a presentation you 
gave in DWF on RPGIV.  I remember because your arrogance and unwillingness to 
listen openly to other ideas astonished me.  Replies like this only serve to 
reinforce that impression.

Rick

-----Original Message-----
From: rpg400-l-bounces+rick.chevalier=americredit.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+rick.chevalier=americredit.com@xxxxxxxxxxxx]On
Behalf Of Bob Cozzi
Sent: Wednesday, February 02, 2005 10:25 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Prototyped Procedures


I think you answered your own question:
>> As a longtime no /copy bigot

Opening up the source after "code freeze" for developers to use is not a
good idea in my opinion. But if you're a one or two-person shop and you
don't worry about other people working with your source, then go for it.
If I did that with RPG xTools, I would have had to have shipped everyone the
entire source library rather than just the prototypes.
To me, though, it is confusing and gimmicky to use this "technique". You can
program-describe your files which is exactly the same thing in my opinion,
to putting all the prototypes in the same source member as the
implementation.
I'm guessing you're using SEU to edit your code... this all-in-one-source
mentality runs rapid in SEU users.

-Bob


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Rick.Chevalier@xxxxxxxxxxxxxxx
Sent: Wednesday, February 02, 2005 9:47 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: Prototyped Procedures


Normally I try to stay out of these discussions but I'm curious about
something.

As a longtime no /copy bigot I'm still coming to terms with using /copy (or
/include) for prototypes.  I have used the method Joe describes (at least I
think it's the same) and I don't see the difference between that and a
separate copybook other than using /define statements.  I actually kind of
like that because then I know exactly what is being copied.

For instance:

Module code

/IF prototypename
d Proc       pr
d  parm1                 1a
d  parm2                 10i 0
/ENDIF

d Proc       pi
        .
        .
        .

In calling program
/DEFINE prototypename
/COPY sourcefile/modulesource
/UNDEFINE


With the prototype in a separate member you don't have the define (or maybe
you do if there are many prototypes in a single copybook) so you are left
with this:

/COPY sourcefile/modulesource

I just don't see issue with using /DEFINE

Rick


Privileged and Confidential.  This e-mail, and any attachments there to, is
intended only for use by the addressee(s) named herein and may contain
legally privileged or confidential information.  If you have received this
e-mail in error, please notify me immediately by a return e-mail and delete
this e-mail.  You are hereby notified that any dissemination, distribution
or copying of this e-mail and/or any attachments thereto, is strictly
prohibited.

-



Privileged and Confidential.  This e-mail, and any attachments there to, is 
intended only for use by the addressee(s) named herein and may contain legally 
privileged or confidential information.  If you have received this e-mail in 
error, please notify me immediately by a return e-mail and delete this e-mail.  
You are hereby notified that any dissemination, distribution or copying of this 
e-mail and/or any attachments thereto, is strictly prohibited.