Re: [perl #33129] N registers get whacked in odd circumstances

Dan Sugalski (via RT) wrote: You'll note that N5 is set to 22253 when the returncc's done, but after the return the value is -21814.6. Looks like something's stomping the N registers. The program below shows exactly the same behavior WRT __set_number_native. The call comes from inside of the mmd

Re: MMD and VTABLE_find_method

Sam Ruby wrote: Leopold Toetsch wrote: However, from : Whenever you make a call using subroutine call syntax, it's a candidate for multiple dispatch. I read this to mean that the *caller* does nothing to distinguish between calls to si

Re: P5 is the new P2

Matt Fowles wrote: P5 is the new P2 Sam and Leo came to the conclusion that the current object should be passed in P5 as well as P2. Currently they are waiting for Dan... Nudge, Nudge... I've implemented this, but I am near the point of recanting. Examples

Re: MMD and VTABLE_find_method

Leopold Toetsch wrote: Sam Ruby wrote: Leopold Toetsch wrote: However, from : Whenever you make a call using subroutine call syntax, it's a candidate for multiple dispatch. I read this to mean that the *caller* does nothing to distingu

Re: cvs commit: parrot/dynclasses pybuiltin.pmc pyclass.pmc pyfunc.pmc pylist.pmc pynone.pmc

Sam Ruby <[EMAIL PROTECTED]> wrote: > --- nci.pmc 7 May 2004 10:33:26 - 1.27 > +++ nci.pmc 20 Dec 2004 22:27:11 - 1.28 > +=item C > + > +Return attribute named C. > + > +=cut > + > +*/ > + > +PMC* get_attr_str(STRING* idx) { > +return VTABLE_g

Re: cvs commit: parrot/dynclasses pybuiltin.pmc pyclass.pmc pyfunc.pmc pylist.pmc pynone.pmc

Leopold Toetsch wrote: Sam Ruby <[EMAIL PROTECTED]> wrote: --- nci.pmc7 May 2004 10:33:26 - 1.27 +++ nci.pmc20 Dec 2004 22:27:11 - 1.28 +=item C + +Return attribute named C. + +=cut + +*/ + +PMC* get_attr_str(STRING* idx) { +return VTABLE_getprop(

Re: MMD and VTABLE_find_method

Sam Ruby wrote: Leopold Toetsch wrote: A few things to note: "foo" is a PMC. It therefore is an object. It can have state (properties, attributes, etc). It can "know" how many arguments are involved in multiple dispatch. The MMD information can't hang off the Sub PMCs. How do you find the co

Re: cvs commit: parrot/dynclasses pybuiltin.pmc pyclass.pmc pyfunc.pmc pylist.pmc pynone.pmc

Sam Ruby wrote: Leopold Toetsch wrote: What is the rational for this pythonism in Parrot core? +The line of code in test case t/pie/b3 that motivates this is: + + print "using", cmp.__name__ + +Where cmp may be a NCI subroutine. Python's builtin "cmp" is basially a Sub PMC. Parrot Sub's have alre

Re: [perl #33129] N registers get whacked in odd circumstances

At 10:56 AM +0100 12/21/04, Leopold Toetsch wrote: Dan Sugalski (via RT) wrote: You'll note that N5 is set to 22253 when the returncc's done, but after the return the value is -21814.6. Looks like something's stomping the N registers. The program below shows exactly the same behavior WRT __set_n

Re: [perl #33129] N registers get whacked in odd circumstances

Dan Sugalski wrote: At 10:56 AM +0100 12/21/04, Leopold Toetsch wrote: The program below shows exactly the same behavior WRT __set_number_native. The call comes from inside of the mmd_fallback function, so I presume that in the part before the shown trace you are having some kind of mathematica

700 tests for PGE

[Markus == [EMAIL PROTECTED] on Mon, 20 Dec 2004 13:59:57 +0200] Markus> I was wondering if it would make sense to add the original Markus> 're_tests' file to parrot distribution, with a script which Markus> autogenerates 're_tests.t' from it. To me, it certainly would. I would note, howev

Re: Let the hacking commence!

Patrick R. Michaud writes: > > rule identifier() { <> \w* } > > Does Perl 6 allow leading underscores in identifiers? If so, > shouldn't this be > > rule identifier() { <++[_]> \w* } > > ? Yeah, it should. There was an error anyway: rule identifier() { <+> \w* } Fixed. > > > rule open_

Re: MMD and VTABLE_find_method

Leopold Toetsch wrote: Sam Ruby wrote: Leopold Toetsch wrote: A few things to note: "foo" is a PMC. It therefore is an object. It can have state (properties, attributes, etc). It can "know" how many arguments are involved in multiple dispatch. The MMD information can't hang off the Sub PMCs.

Re: cvs commit: parrot/dynclasses pybuiltin.pmc pyclass.pmc pyfunc.pmc pylist.pmc pynone.pmc

Leopold Toetsch wrote: Sam Ruby wrote: Leopold Toetsch wrote: What is the rational for this pythonism in Parrot core? +The line of code in test case t/pie/b3 that motivates this is: + + print "using", cmp.__name__ + +Where cmp may be a NCI subroutine. Python's builtin "cmp" is basially a Sub PMC.

Re: Test::Legacy warnock'd

On Tue, Dec 21, 2004 at 04:53:18PM +0100, Tels wrote: > On Tuesday 21 December 2004 08:53, Michael G Schwern wrote: > > I've gotten absolutely no response about Test::Legacy. Is anybody > > using it? Anybody tried migrating old Test.pm based tests with it? > > I am converting my old tests direct

Re: Test::Legacy warnock'd

Michael G Schwern wrote: > On Tue, Dec 21, 2004 at 04:53:18PM +0100, Tels wrote: > >>On Tuesday 21 December 2004 08:53, Michael G Schwern wrote: >> >>>I've gotten absolutely no response about Test::Legacy. Is anybody >>>using it? Anybody tried migrating old Test.pm based tests with it? >> >>I

Re: Test::Legacy warnock'd

On Tue, Dec 21, 2004 at 12:56:27PM -0500, Geoffrey Young wrote: > > There's no "I want to add a new test to this test file that uses Test.pm and > > it would be nice if I could use Test::Foo" case? > > I could see this being really good for Apache-Test, which is by default > Test.pm driven. the t

Re: Test::Legacy warnock'd

> But for all Test::Builder based modules you can get the same intent with > Test::Builder->reset. yup, I used that for the port away from Test.pm - works like a charm :) --Geoff

Re: Test::Legacy warnock'd

On Tue, Dec 21, 2004 at 06:09:40PM +0100, Tels wrote: > Granted, that was what I did before Test::Legacy, which seems to have gone > from a wild idea to some working stage while I was not looking :) Most of it was written in about an hour and a half late one night with another hour worth of polish

Re: Test::Legacy warnock'd

On Tue 21 Dec 2004 18:32, Michael G Schwern <[EMAIL PROTECTED]> wrote: > On Tue, Dec 21, 2004 at 04:53:18PM +0100, Tels wrote: > > On Tuesday 21 December 2004 08:53, Michael G Schwern wrote: > > > I've gotten absolutely no response about Test::Legacy. Is anybody > > > using it? Anybody tried migr

[PATCH] Stomp a warning in pybuiltin.pmc

The attached patch fixes this warning in pybuiltin.pmc: pybuiltin.pmc: In function `make_type': pybuiltin.pmc:76: warning: declaration of `nameprop' shadows previous local Simon --- dynclasses/pybuiltin.pmc.oldTue Dec 21 15:30:01 2004 +++ dynclasses/pybuiltin.pmcTue Dec 21 15:3

Re: Test::Legacy warnock'd

-BEGIN PGP SIGNED MESSAGE- Moin, On Tuesday 21 December 2004 08:53, Michael G Schwern wrote: > I've gotten absolutely no response about Test::Legacy. Is anybody > using it? Anybody tried migrating old Test.pm based tests with it? I am converting my old tests directly to Test::More (Tes

Re: Test::Legacy warnock'd

-BEGIN PGP SIGNED MESSAGE- Moin, On Tuesday 21 December 2004 18:32, Michael G Schwern wrote: > On Tue, Dec 21, 2004 at 04:53:18PM +0100, Tels wrote: > > On Tuesday 21 December 2004 08:53, Michael G Schwern wrote: > > > I've gotten absolutely no response about Test::Legacy. Is anybody > >

Re: Test::Legacy warnock'd

-BEGIN PGP SIGNED MESSAGE- Moin, On Tuesday 21 December 2004 19:35, Michael G Schwern wrote: > On Tue, Dec 21, 2004 at 06:09:40PM +0100, Tels wrote: > > Granted, that was what I did before Test::Legacy, which seems to have > > gone from a wild idea to some working stage while I was not lo

Re: Auto My?

On Mon, 20 Dec 2004, James Mastros wrote: OTOH, I realize now you can do that with zip in P6, in which case you do have a mention of the whole variable to stick a my on -- C I think C reads better though, even though looking at it literally, you're attempting to lexicalize an element. But dealin