On Sun, Mar 23, 2003 at 11:11:54AM +0100, Leopold Toetsch wrote:
This is a first step in hiding vtable functions - not only: Using these macros also provides more readable source files:
return VTABLE_1(getprop, (PMC*) SELF->data, key);
..., and make it easy to change how the vtables are called in future.
This is the main reason for it.
1: It's documented what we are doing here 2: It's only 1 layer of macros (not 4 or more, as perl5 can manage) 3: We don't have the cruft of macros no longer needed but kept for source compatibility cluttering up our header files.
Full ACK.
As these are code generated, are we able to conditionally write these out as inline functions? This would make debugging easer.
Not really, but I don't see, how this set of macros would influence debugging negatively.
Nicholas Clark
leo
