Sam Ruby wrote:
A patch is attached, but it bears a little discussion.
Well, that didn't exactly work. I've since commmitted these patches,
and more. A the moment, all the python and pirate unit tests pass. (Woot!)
In the absense of other direction, I plan to write more tests and use
them to drive the evolution of object.c and related sources. A
description of my current thinking can be found at[1], but I am open to
any implementation which continues to pass the tests that I define. In
fact, the unit tests can change, as long as alternatives are provided
that I can build upon to get the desired functionallity as defined by
the pirate tests.
Now that dynclasses build as a part of the 'all' target, I'm planning on
adding the dynclass tests to the 'test' target. I've noticed that the
test target is not successful unless the all target had been built
previously, so this should not be a problem. If anybody has an issue
with this then perhaps a 'testall' target can be defined.
- Sam Ruby
[1] http://www.intertwingly.net/blog/2004/11/14/Parrot-classes
