Another option I wouldn't be too adverse to would be to have a NULL
class method on the .Pointer class, which would allow you to pass
.pointer~null for a null value.
Rick
On Mon, Oct 12, 2009 at 4:29 PM, David Ashley
wrote:
> The pointer class does not allow me to create a pointer instance from
On Mon, Oct 12, 2009 at 1:29 PM, David Ashley
wrote:
> The pointer class does not allow me to create a pointer instance from
> Rexx code.
You could do this, which is what I did in ooDialog, but Rick may not approve.
In the very first init of ooDialog, in the C++ code I create a null
.Pointer ob
I'd just pass the object type and manage it that way...or else just
signal a null pointer with an omitted argument and make the pointer
value optional. An poptional pointer value comes through as NULL if
not specified.
Rick
On Mon, Oct 12, 2009 at 4:29 PM, David Ashley
wrote:
> The pointer clas
The pointer class does not allow me to create a pointer instance from
Rexx code. So unless a NULL pointer is returned from a method/function
API I can not get access to a NULL pointer. I need some way to pass a
NULL pointer to a method/function API that uses the POINTER argument
type. Otherwise
Why don't you just use a pointr with a value of 0? I even added an
isNull Method to the pointer class already (at your request, I might
add) to give special processing for null pointers.
Rick
On Mon, Oct 12, 2009 at 4:13 PM, David Ashley
wrote:
> I have several instances in the RexxGTK project
I have several instances in the RexxGTK project where I need to pass a
NULL pointer from the Rexx code to an API. The underlying C API uses a
Null pointer to indicate that we are finished calling that API in a
repetitive fashion.
It would be really nice if The Rexx subsystem could use the .nil
