[perl #40102] [BUG] Using splice with an out-of-range array index gives bad error

2006-08-06 Thread via RT
# New Ticket Created by Matt Diephouse # Please include the string: [perl #40102] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=40102 > mini:~/Projects/parrot mdiep$ cat test.pir .sub main :main $P0 = new .Array

Re: Re: a premature optimization

2006-08-06 Thread Matt Diephouse
Will Coleda <[EMAIL PROTECTED]> wrote: On Aug 6, 2006, at 4:08 PM, Leopold Toetsch wrote: >> invalid_1559: >>.local pmc interactive >>interactive = get_root_global ['tcl'], '$tcl_interactive' > > # you might cache that once - it's probably used in zillion of places > This is a user vis

Re: [EMAIL PROTECTED]: tru64 core dump: t/examples/japh_12.pasm

2006-08-06 Thread xinhua liu
un-subscribe On 8/4/06, Chip Salzenberg via RT <[EMAIL PROTECTED]> wrote: Fixed in svn by deleting that never-will-work-again japh, which hacked internals in an amazingly evil way.

Re: [perl #40058] Disambiguate usage of class PMCs from class name lookup (pdd15, pdd06, pdd19)

2006-08-06 Thread chromatic
On Sunday 06 August 2006 16:57, Martin Kealey wrote: > The naive reaction to this is that if you define ['myHLL';'foo'] then > whether ['parrot';'foo'] is defined (or later becomes defined) is of no > concern. If my code depends on the undefinedness of certain symbols, and those symbols may or m

Re: [perl #40058] Disambiguate usage of class PMCs from class name lookup (pdd15, pdd06, pdd19)

2006-08-06 Thread Martin Kealey
On Sun, 6 Aug 2006, chromatic wrote: > > Any reason to treat HLL namespaces differently from classes, at > > least in respect of being an inheritance hierachy? > Preventative measures against future additions to 'parrot' breaking > your code without your knowledge. It's the same reason many langu

Re: [perl #40058] Disambiguate usage of class PMCs from class name lookup (pdd15, pdd06, pdd19)

2006-08-06 Thread chromatic
On Sunday 06 August 2006 16:00, Martin D Kealey wrote: > Any reason to treat HLL namespaces differently from classes, at least in > respect of being an inheritance hierachy? Preventative measures against future additions to 'parrot' breaking your code without your knowledge. It's the same reaso

Re: [perl #40058] Disambiguate usage of class PMCs from class name lookup (pdd15, pdd06, pdd19)

2006-08-06 Thread Martin D Kealey
On Thu, 3 Aug 2006, Chip Salzenberg wrote: > KNOWN FUTURE DEVELOPMENTS > > It's already decided that we're moving class PMCs into the normal namespace > tree. This change will eliminate many uses of the class-lookup opcodes, but > not all: There's a two-level search will still be required, where t

Re: a premature optimization

2006-08-06 Thread Will Coleda
On Aug 6, 2006, at 4:08 PM, Leopold Toetsch wrote: Am Sonntag, 6. August 2006 19:03 schrieb Will Coleda: we get a 9K line PIR sub. Running this through parrot dies after about 2.5m on an runtime error on one of the tests. Great progress. While Parrot shouldn't die or - in the long run - ta

Re: a premature optimization

2006-08-06 Thread Leopold Toetsch
Am Sonntag, 6. August 2006 22:08 schrieb Leopold Toetsch: >       $P1565 = 'for_each'($P1560, $P1561, $P1563) 'foreach' of course. Sorry, leo

Re: a premature optimization

2006-08-06 Thread Leopold Toetsch
Am Sonntag, 6. August 2006 19:03 schrieb Will Coleda: > we get a 9K line PIR sub. Running this through parrot dies after > about 2.5m on an runtime error on one of the tests. Great progress. While Parrot shouldn't die or - in the long run - take really long to compile that, you could work a bit o

a premature optimization

2006-08-06 Thread Will Coleda
Ok. I've recently converted much of partcl's test suite over to "pure tcl". Instead of using a perl based test script, the tests are now written in tcl, using a very small test::more like script. Now we can more easily run the tests from tcl's own test suite, and easily use tclsh to run ou

Continuations and inferior runloops: Analysis and POC

2006-08-06 Thread Bob Rogers
The problem is that inferior runloops cannot be re-entered via continuation. One example (out of many) is the delegate pmclass, which uses inferior runloops in vtable methods to run bytecode. The resulting call structure (mixing bytecode and C) looks like this: main runloop => mai