On Jun 21, 2007, at 1:39 AM, Allison Randal wrote:
Andy Lester wrote:
I guess I don't see the need to document a standard C behavior
with a macro.
If you had read all the way through the message, you would see that
the biggest benefit is the ability to hang debugging hooks off the
macro.
We have a number of these kinds of debugging hooks throughout
Parrot (src/gc/memory.c is a good example).
No, I saw that, too. My point was just about documentation.
If we're set on using a macro for doing struct copies, then it needs
to handle copying multiple structs, since there a bunch of places
we're doing memcpy()s with math for multiple structs. I'll work on
that today. Getting rid of the math may be the best reason to use a
macro yet.
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
