Re: [dtrace-discuss] Question on dtrace -C behavior

[Ryan Johnson]

After a bit of playing around it appears that dtrace doesn't implicitly 
expand 'long' to its real type (which is 'long int') and the missing 
'int' triggers the error. For example:

typedef unsigned u; // error
typedef unsigned int ui; // works
typedef unsigned long; // error
typedef unsigned long int uli; // works

I have no clue why the problem wouldn't affect header files, though.

Ryan

_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org