On Apr 5, 2007, at 5:45 PM, Leopold Toetsch wrote:
Am Donnerstag, 5. April 2007 00:39 schrieb Jonathan Worthington:
Don't really need a policy to tell me that breaking stuff for
languages
folks sucks. :-) I try hard to avoid it, but unfortunately stuff slips
through the net occasionally. In this case, I wasn't even aware that
you
could use SELF.meth(...) to call non-vtable methods, and it's done
nowhere in core PMCs or I'd have noticed it.
This could be also read as a notice to language maintainers:
If you are using some "features" of parrot, then please, please submit
a core
test for it, if such a test doesn't exist yet. This will help Parrot
and You
in the future ...
Thanks.
leo
Not only to language maintainers, but anyone using parrot where a
"feature" isn't tested. And it also technically falls on whoever
implemented said "feature" in parrot, for not adding a test.
What if we had a repository, ala pugs with it's "open" commits, solely
for people to commit tests. It could help improve bug discovery and
test coverage, as well as ambiguity about features in parrot. Then
developers could just update it and run it seperately(and check it to
make sure nothing malicious gets through which is always a potential of
course).
