RE: Exported Variables (was Long Constant Names)

Paul,

So I have an understanding about what you're suggesting if a variable in
a procedure interface changes, can you give me an example of bad vs.
good?  So I'm clear in my understanding of a variable change, let's use
the example of a 1A code field being changed to 3A to allow for more
permutations and possibly a more mnemonic meaning within the code (not
looking to discuss the validity of such a change, just how it would be
accommodated in the interface).

Thanks!
Kurt Anderson
 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Morgan
Sent: Friday, January 07, 2005 9:47 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Exported Variables (was Long Constant Names)

Barbara,

Pass-by-copy would be best.  Good to see that it's on a future
enhancment list.

BTW, I object to using LIKE definition in a prototype because:

1) It violates the idea of a procedure as being immutable.  If the
interface changes it requires retesting.  You want to avoid changing the
interface at all costs.  Better to write a new replacement interface if
the variable changes. (this also applies to LIKE definitions in a
procedure interface)

2) It sort of defeats the purpose of encapsulation.  Another variable
must be brought out of the internals of the procedure just to use the
prototype.
Why make me code a data structure or variable just to define a parameter
in a prototype?  More extra variables I don't really need in my calling
program.  Makes the procedure unwieldily.

Paul

--
Paul Morgan
Senior Programmer Analyst - Retail
J. Jill Group
100 Birch Pond Drive, PO Box 2009
Tilton, NH 03276-2009
Phone: (603) 266-2117
Fax:   (603) 266-2333
"Barbara Morris" wrote

> I think CONST is working correctly to stop the compile.  (We do have a

> "pass by copy" parameter-passing-mode on our possible future 
> enhancements list.)
>
> Defining the parameter-passing temporary LIKE the constant would only 
> work if it was the same type as the prototyped parameter. I guess it 
> would be a good practice to define every by-reference prototyped 
> parameter LIKE or LIKEDS something, so that temporaries could be 
> easily defined LIKE or LIKEDS the same thing.
>
>  D myproc_types         ds              qualified
>  D                                      based(typedef_dummy)
>  D   myparm                        10a
>
>  D myproc               pr
>  D   myparm                             like(myproc_types.myparm)
>
>  ...
>
>  D myparmTemp           s               like(myproc_types.myparm)

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



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