Re: Null values and WSDL2RPG and HTTPAPI?

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Thomas,

Sure I can see that need...

At the same time, I see developers complaining about having to set the
.value and .isNull subfields....just seems like an implementation
detail worth hiding...if for no other reason than the fact that one
day RPG may get true NULL support....

What if we defined a "handle" or pointer that could be passed between
the user procedures' and into the Getters/Setters?

Probably would need a New() procedure that returns the
handle/pointer....but you might even be able to offer a New() that
takes individual *OMMITable parameters.

Just some thoughts...
Charles



On Wed, Jan 5, 2011 at 2:47 PM, Thomas Raddatz
<thomas.raddatz@xxxxxxxxxxx> wrote:
> Charles,
>
> I greatly appreciate your feedback because you had some good ideas. To be
> honest I do not tend to go with that special "setter" procedures because
> people may want to pass the request or response message between their
> procedures. Obviously that would be impossible with a stub internal data
> structure.
>
> But I like your "t_Int4_Nullable" idea. Today I generate the following code
> for an array element like this:
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------