Dan Sugalski <[EMAIL PROTECTED]> wrote: > At 4:54 PM -0500 2/25/04, Simon Glover wrote: >> If I'm understanding the docs correctly, this should print '0'. >> Instead, it prints 'Array index out of bounds!'
> Another bug, though the offset ought to be 2 right now. (Attributes 0 > and 1 are taken by other things so they're valid) *Please* don't. C<classoffset> (and attribute access) should by all means start with 0. - Let's hide the internals - If that offset is ever changed, existing code will break - Its ugly We can afford one more instruction ( offset += POD_FIRST_ATTRIB; ) that's just one CPU cycle. leo
