Mark,
I think there may still be a small misunderstanding on your part on
how some of this works. I noticed the following snippet from your
last checkin:
/**
- * Return the number of existing arguments passed to a native API Rexx method,
- * (as opposed to the size of the argument array.)
+ *
On Fri, Dec 5, 2008 at 3:39 AM, Rick McGuire [EMAIL PROTECTED] wrote:
I think there may still be a small misunderstanding on your part on
how some of this works.
Well, yeah there was. grin
argumentExists() applies only to the arguments passed to the native
method, and that includes any
Yes, context-GetArguments() returns an ooRexx array containing the
raw, unprocessed argument objects originally passed to the method.
Since the ArrayAt() API returns NULLOBJECT if an element does not
exist, this is a reliable test for if the argument is there. This is
basically equivalent to the
Hi Rick,
It seems to me that the argumentExists() is behaving different than it
did several months ago. I don't see any recent changes that might
cause this.
Since it wasn't documented, I think I originally just experimented to
see what was what. Take this method signature:
RexxMethod6(
argumentExists() functions like the ARG() BIF. The argument values
are are origin 1, not origin 0. So the margin is the 5th argument,
as you've specified it in your signature. The pseudo-arguments such
are counted here too, so argumentExists(5) is the correct thing to
specify.
Rick
On Thu,
On Thu, Dec 4, 2008 at 2:39 PM, Rick McGuire [EMAIL PROTECTED] wrote:
argumentExists() functions like the ARG() BIF. The argument values
are are origin 1, not origin 0. So the margin is the 5th argument,
as you've specified it in your signature. The pseudo-arguments such
are counted here
