[DGD] #define peculiarity? THanks :)

[Michael McKiel]

 --- Kris Van Hees <aedil at alchar.org> wrote: 
> The sscanf() has nothing to do with this.  Your define will expand in
> code where it is used as object target for a call like this:
> 	"/k"+"/system/"+"userd"->somefunction(...)
> Which is interpreted as a call to "userd"->somefunction(...), and the
> The better way to do this is to change the define to be:
> 	#define USERD	(KERNEL_DIR+SYSTEM_DIR+"userd")

Guess I shoulda waited heh, just sent off another long msg, as I had tested
on an unmodified KLib too...and mildly resented 'not debugging' heh.
I just used the sscanf as an example to the issue, of why is it legal there
and not for the object call, I didn't consider the brackets :)

The error had such poor output I really couldn't debug it, as at the point
where it occured, I as well did a 
if (!::find_object("/k/system/userd")) ::find_object(DRIVER)->message("NO
USERD!!");
Just before the call to the previously "def'd" USERD-> call would of occured.
And that didn't msg off, so it really had me boggled.

Thanks.

______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca
_________________________________________________________________
List config page:  http://list.imaginary.com/mailman/listinfo/dgd