×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I think the problem is on the *nopass parameter. A *nopass parameter could
have a non-null address even when caller is not passing the parm. But if
you attempt to access the parm, the program breaks. That is the reason why
we can't simply check "if %addr(param) <> *null" for *nopass parameter. For
a *nopass parameter, we have to also check if %parm(param2) <= 2 .... quite
annoying....
"Charles Wilt" <charles.wilt@xxxxxxxxx> wrote in message
news:mailman.32986.1299613718.2702.rpg400-l@xxxxxxxxxxxx...
Basically I mean there's no way to define a standalone null capable
variable...
Using *OMIT:*NOPASS means jumping though hoops when you need to just
pass them along to other procedures...
In the OP's case, I could see where better null support would allow
proc1 to just call proc2 (disregarding the differences in type for
parm1).
Charles
On Tue, Mar 8, 2011 at 2:06 PM, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
wrote:
On 3/8/2011 12:51 PM, Charles Wilt wrote:
There isn't an easy way...since RPG doesn't offer true null support...
No idea what this means. Can you elaborate?
--
This is the RPG programming on the IBM i / System i (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 mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
