Re: Auto My?

2004-12-18 Thread Luke Palmer
JOSEPH RYAN writes: > As bad of an idea that I think this is, I wonder if Perl6's reflection > capabilities will be powerful enough to where a module/pragma could be > written that would be able to do this? For instance, one idea was: > lexically change the current grammar to a subclass of the gra

Re: Auto My?

2004-12-18 Thread JOSEPH RYAN
- Original Message - From: Luke Palmer <[EMAIL PROTECTED]> Date: Saturday, December 18, 2004 4:16 pm Subject: Re: Auto My? > Rod Adams writes: > There are pros and cons, and it basically ends up being a design > choice. > > Well, at least when strictures are on. When they are off, the >

Re: PGE tests wanted (was P6GE tests wanted)

2004-12-18 Thread Patrick R. Michaud
On Sat, Dec 18, 2004 at 08:47:42AM -0800, Larry Wall wrote: > : This test seems to cause an infinite loop > : (with parrot_2004-12-16_160001) > : > : p6rule_isnt('a--', '^[a?b?]*$', 're_tests 387 (#438)'); # infinite loop > > Detecting failure to progress can be quite tricky, actually. It's eas

Re: Auto My?

2004-12-18 Thread Juerd
Rod Adams skribis 2004-12-18 14:55 (-0600): > Considering that "proper" and common usage, not to mention strictures, > dictates a heavy insistence on 'my'. I will thus assume that creation of > lexical variables with 'my' far out numbers the creation of package > space globals. Should we not the

Re: Auto My?

2004-12-18 Thread Luke Palmer
Rod Adams writes: > Considering that "proper" and common usage, not to mention strictures, > dictates a heavy insistence on 'my'. I will thus assume that creation > of lexical variables with 'my' far out numbers the creation of package > space globals. Should we not then have it where it's the defa

Auto My?

2004-12-18 Thread Rod Adams
Considering that "proper" and common usage, not to mention strictures, dictates a heavy insistence on 'my'. I will thus assume that creation of lexical variables with 'my' far out numbers the creation of package space globals. Should we not then have it where it's the default behavior, and crea

700 tests for PGE

2004-12-18 Thread Markus Laire
Here are 700 tests for pge, autoconverted from 're_tests' file, from perl5 source. If there are any significant errors in these tests, please tell, and I can correct the script. Original perl5-tests are in comments so it's quite easy to see if there has been an error in converting. After comme

Re: PGE tests wanted (was P6GE tests wanted)

2004-12-18 Thread hv
Larry Wall <[EMAIL PROTECTED]> wrote: :Henry Spencer's original regex routines simply disallowed expressions :that might be infinite. We tried relaxing that in Perl 5, and got :it wrong more than one way. I'm not actually sure what approach p5 :takes right now, if any. We detect and warn of repe

Re: PGE tests wanted (was P6GE tests wanted)

2004-12-18 Thread Larry Wall
On Sat, Dec 18, 2004 at 12:16:31PM +0200, Markus Laire wrote: : Patrick R. Michaud wrote: : >>Larry mentioned 're_tests' file from perl5-source. Is anyone working on : >>it currently? I could make a simple script to convert at least some of : >>it to this pge-testing format which uses p6rule_* :

Re: need help

2004-12-18 Thread James E Keenan
Sridhar Subbarayan wrote: Hi, I am urgently in need of some study material that deals with using perl in QA process. How is functionality testing done using perl. How is performance testing done using perl. How does perl help in automation. Please give some examples. Please let me know if there ar

Re: [perl #33092] IMCC sub/opcode invocation conflict

2004-12-18 Thread Leopold Toetsch
Dave Brondsema wrote: "print"("hello") That looks really great, but when I try it in 0.1.1 (on Windows), I get: error:imcc:parse error, unexpected '(', expecting '\n' You'd need latest from CVS, sorry. leo

Re: PGE tests wanted (was P6GE tests wanted)

2004-12-18 Thread Patrick R. Michaud
On Sat, Dec 18, 2004 at 12:16:31PM +0200, Markus Laire wrote: > > This test seems to cause an infinite loop > (with parrot_2004-12-16_160001) > > p6rule_isnt('a--', '^[a?b?]*$', 're_tests 387 (#438)'); # infinite loop So far repeating groups of zero-length strings causes an infinite loop- I jus

Re: [perl #33092] IMCC sub/opcode invocation conflict

2004-12-18 Thread Dave Brondsema
Quoting Luke Palmer via RT <[EMAIL PROTECTED]>: > Dave Brondsema writes: > > # New Ticket Created by Dave Brondsema > > # Please include the string: [perl #33092] > > # in the subject line of all future correspondence about this issue. > > # http://rt.perl.org:80/rt3/Ticket/Display.html?id=330

Re: runops_args vs NCI

2004-12-18 Thread Sam Ruby
Leopold Toetsch wrote: Sam Ruby wrote: However, VTABLE_invoke on NCI methods is where the "real work" is done (including reading from and writing to registers), and a null dest is returned. One more remark: This is classes/nci.pmc:invoke void* invoke (void * next) { Parrot_csub_t func

Re: PGE tests wanted (was P6GE tests wanted)

2004-12-18 Thread Markus Laire
Patrick R. Michaud wrote: Larry mentioned 're_tests' file from perl5-source. Is anyone working on it currently? I could make a simple script to convert at least some of it to this pge-testing format which uses p6rule_* 'simple script' .. it isn't so simple anymore ;) I'm not aware of anyone worki

Re: RT#31859, Plain ole Hash

2004-12-18 Thread Leopold Toetsch
Sam Ruby wrote: Any objections to the NCI methods being removed from Coroutine(next), Hash(fromkeys), Iterator(next), and PerlHash(fromkeys) now? The fromkeys in Hash and PerlHash can be removed. The .next methods in iterable PMCs will be needed generally. But iterators need some rework still, e

Re: [perl #31859] [TODO] Plain ole Hash

2004-12-18 Thread Leopold Toetsch
Bernhard Schmalhofer via RT wrote: The attached patch makes the Hash PMC use basic PMCs by default. Native integers, numbers and strings are now stored as Integer, Float and String PMCs. For keys without values, the Undef PMC is returned, as it is laid out in pdd17. As already mentioned: the Hash

[perl #31859] Re: Plain ole Hash

2004-12-18 Thread Bernhard Schmalhofer via RT
> > The attached patch makes the Hash PMC use basic PMCs by default. Sorry again, one shouldn't send any patches after midnight. First I forgot to clean up cruft from hash_pmc_20041218.patch. Then, trying to send the corrected patch, I misspelled the name of the mailing list. So, please note th

Re: runops_args vs NCI

2004-12-18 Thread Leopold Toetsch
Sam Ruby wrote: However, VTABLE_invoke on NCI methods is where the "real work" is done (including reading from and writing to registers), and a null dest is returned. One more remark: This is classes/nci.pmc:invoke void* invoke (void * next) { Parrot_csub_t func = (Parrot_csub_t)D2FPT