You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is sometimes necessary to determine whether a
values passed to a UDF is NULL. The current approach
which passes parameters by value prohibits this test --
a NULL is passed as an empty value, which can't be
distinguish from a 'real' empty/zero value.
The text was updated successfully, but these errors were encountered:
From Claudio: I implemented DESCRIPTORS as UDF parameters.
The verb "implement" is misleading there: I only uncovered
the feature previously available only to GDML definitions
and added DESCRIPTORS as a return mechanism. This small
addition is only for writing UDFs in a slightly
simpler way (IMHO, of course), it doesn't mean you can
change the type of the return parameter as set in the UDF
declaration (or definition).
The reason I couldn't change normal BY REFERENCE parameters
to be the null pointer (or nil) when the parameter is NULL
is because there are a lot of UDFs written already and they
don't expect a null pointer but zero or empty string, so I
would have broken all of them. But when working with
descriptors, the engine already passed a null pointer to
signal NULL, before I touched it.
In fact, the [almost silently] posted FBUDF relies on
descriptors and seems to work well. I intended it to be
pushed into a subdir of the extlib one but since the WinCVS
client is not very intuitive and inconsistent (but better
than nothing or having to remember 10 command-line params
for me), the files appeared in the same extlib directory.
Submitted by: Sean Leyne (seanleyne)
Assigned to: Claudio Valderrama C. (robocop)
SFID: 446208#
Submitted By: seanleyne
It is sometimes necessary to determine whether a
values passed to a UDF is NULL. The current approach
which passes parameters by value prohibits this test --
a NULL is passed as an empty value, which can't be
distinguish from a 'real' empty/zero value.
The text was updated successfully, but these errors were encountered: