Re: PI replaces *entry Plist

[rob@xxxxxxxxx]

I agree here.  I would recommend against using 'like' in a prototype, 
unless 1, or more, of a few conditions exist.
1 - The prototype is strictly internal
2 - You're one of those shops that always also /COPYs in some standard 
variables and can make it like one of those.  Like those shops whose DDS 
requires to be ref'd and their FREF has various generic variables.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Joep Beckeringh <joep@xxxxxxxxxxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
03/17/2004 02:15 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: PI replaces *entry Plist






Dave Boettcher wrote:
> Thanks for the answer.  Actually that is similar to the archive I found
> that prompted the question.  CODE said that the PR could not use "like".

I just tested, but CODE did not have any problem with 'like' in a 
prototype. 
BTW: you refer to 'someting' in your definition; should be 'something'; 
but 
that's probably a typo and I don't think CODE checks that.

Personally I never use 'like' in a prototype. The prototype is the 
interface to 
'the outside world' and should be clear and unambiguous about the data 
types the 
program or procedure expects.

Joep Beckeringh
_______________________________________________
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.