|
On 3/9/2011 8:57 AM, Charles Wilt wrote:
My point is that *NOPASS is only a problem because IBM implemented it
that way. :)
I'm sure Barbara and co. had good reasons...but I can't help but think
that part of issue was RPG's limited support of NULL. After all
options(*NULLIND) didn't come around till v5r4 and you still can't
define a stand-alone null variable.
Even if RPG had had great support for NULLIND, I don't think it would
have led to *NOPASS somehow making the parameter null capable.
Other languages besides RPG (like C with its ..., or program APIs)
support the notion of parameters that are simply not passed.
--
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.
As an Amazon Associate we earn from qualifying purchases.
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.