RE: creating a new procedure thatcallanexistingprocedurewithoneadditional parm

MyProc(parm1:*omit);

Places two parameters on the call stack, one of which happens to be *NULL.

MyProc(parm1);

Only places one parameter on the call stack.


One reason for the difference AFAIK, you can't use *OMIT with a parameter 
passed by VALUE.


Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Paul Morgan
> Sent: Wednesday, July 27, 2005 10:54 AM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: Re: creating a new procedure
> thatcallanexistingprocedurewithoneadditional parm
> 
> 
> Barbara,
> 
> Is this requirement to check %Parm more to do with ILE or 
> with RPG?  Why
> wouldn't the call using *NOPASS work like using *OMIT?
> 
> Use the example Charles gave in another message why should:
> 
> MyProc(parm1:*omit);
> MyProc(parm1)
> 
> be any different?
> 
> 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 wrote
> 
> > I think Charles was talking about the value of an unpassed (*nopass)
> > parameter.  A little test had shown that if you don't even pass the
> > parameter, the address is null, but that little test only 
> demonstrated
> > that the address is _sometimes_ null.
> 
> 
> 
> -- 
> 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.
> 
>