Before you release 1.0.3 -- please!

Before you release 1.0.3 -- please!

[Mark Schaefer]

    ECGS developers,

    Before you send the next release out the door, could someone figure
out what you're going to do about the NULL problem.  Basically, it's a
damned if I do, damned if I don't problem.

    Since you use __null, which is a "magic pointer entity" that can
supposedly point to anything.  I've discovered that it's not very good
at pointing to, say, class member functions.

A test case is attached.  This one I actually verified to have the
error.

test1.C
[schaefer@liz]$ gcc -o test1 test1.C
test1.C: In function `int main(int, char **)':
test1.C:18: cannot convert `0' from type `{unknown type} *' to type
`void (UiCallbackHandler::*)(int, int, int)'

test2.C
[schaefer@liz]$ gcc -o test2 test2.C
test2.C: In function `int main(int, char **)':
test2.C:18: no matching function for call to
`UiCallbackHandler::addCallback (int, int, const int &, int)'
test2.C:11: candidates are: UiCallbackHandler::addCallback(int, int,
void (UiCallbackHandler::*)(int, int, int), int)

Note: (after switching the include to <sys/types.h>, both examples
compile on the SGI 7.2 compiler).
They should compile on any ANSI C++ standard (or nearly standard)
compiler.

Please, oh please figure out something to do with this!

--
Mark Schaefer

Re: Before you release 1.0.3 -- please!

[Joe Buck]

>     Before you send the next release out the door, could someone figure
> out what you're going to do about the NULL problem.  Basically, it's a
> damned if I do, damned if I don't problem.

The workaround is to use 0 in your code for function pointers or
member function pointers.  I doubt if this is going to be fixed before
1.0.3, since the only purpose of 1.0.3 is to fix so-called showstopper
bugs, not bugs with simple workarounds.

> int main(int, char**)
> {
>     UiCallbackHandler a;
>     a.addCallback (1,1,NULL,1);
> }

s/NULL/0/