RE: RPG/400 pgm strange behavior

["Richard Jackson" <richardjackson@xxxxxxxxxxxxxxxxxx>]

Effective if used.  Use is by convention, not enforced.  I'm not knocking
the concept only the implementation.  Don't shoot the messenger

Richard Jackson
mailto:richardjackson@richardjackson.net
www.richardjacksonltd.com
Voice: 1 (303) 808-8058
Fax:   1 (303) 663-4325

-----Original Message-----
From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
Behalf Of Douglas Handy
Sent: Wednesday, July 12, 2000 10:28 PM
To: RPG400-L@midrange.com
Subject: Re: RPG/400 pgm strange behavior


Richard,

>Are the RPG prototypes "externally described"

I typically use /COPY members for prototypes, so in a sense you could
call them "externally described".

>or could I create a program
>with a wrong prototype, compile it successfully, the run the program and
>cause a failure?

Granted, if you created a prototype using ExtPgm and defined the
parameters wrong then used a CALLP consistent with the prototype (but
not consistent with what the program expected), then you're back to
the same potential problem and memory corruption.

However, /COPY prototypes can be created at the same time as the
program or procedure, as part of the original work and testing.  If
they are just included in future programs needing to do the calls, it
provides an effective compile-time safeguard against parameter
mismatchs.

Doug
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---