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
On Friday 06 April 2007 00:58, Joshua Isom wrote:
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
On Apr 6, 2007, at 11:48 AM, chromatic wrote:
On Friday 06 April 2007 00:58, Joshua Isom wrote:
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
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
At 01:33 04/04/2007 +0100, Jonathan Worthington wrote:
Hi,
I was working on starting to move class functionality into v-table
methods, as discussed on list recently. However, I hit an interesting
issue - you cannot have a METHOD or PCCMETHOD with the same name as a
vtable method. We need to
François PERRAD wrote:
Anyway, hope this is agreeable, and please do report any issues.
This new behavior breaks the build of Lua PMC.
For me too, even after a 'make realclean' on Parrot. In the interests of
our developing policy on a stable trunk: Jonathan, fix the problem for
Lua or
Jonathan Worthington wrote:
Hi,
I was working on starting to move class functionality into v-table
methods, as discussed on list recently. However, I hit an interesting
issue - you cannot have a METHOD or PCCMETHOD with the same name as a
vtable method. We need to be able to do that to
François PERRAD wrote:
This new behavior breaks the build of Lua PMC.
Argh, sorry. :-( Thanks for the detailed bug report - I know where the
problem is, and am working on a fix.
Jonathan
Allison Randal wrote:
For me too, even after a 'make realclean' on Parrot. In the interests
of our developing policy on a stable trunk: Jonathan, fix the problem
for Lua or revert the change before continuing with further development.
Don't really need a policy to tell me that breaking stuff
Allison Randal wrote:
This is a leftover from the old days when the way to override a vtable
method was to define a method with an '__' name, so they never
conflicted.
Not really - this was a conflict in the names of the methods at a C
level. The '__' prefix was a PIR-level thing. In PIR we
Jonathan Worthington wrote:
Anyway, fixed in r17982. May need a realclean - I had to do one anyway
to run the buildtools tests.
Awesome. Works for me even without realclean.
Thanks!
Allison
Hi,
I was working on starting to move class functionality into v-table
methods, as discussed on list recently. However, I hit an interesting
issue - you cannot have a METHOD or PCCMETHOD with the same name as a
vtable method. We need to be able to do that to implement the interface
specified
12 matches
Mail list logo
