Re: Call for B0rked

2005-09-13 Thread Patrick R. Michaud
On Tue, Sep 13, 2005 at 08:58:49AM -0400, Matt Diephouse wrote: > Leopold Toetsch <[EMAIL PROTECTED]> wrote: > > > Also, is rx.ops obsolete? PGE seems to be the new solution. If so, can > > > we get rid of rx.ops? Or is rx.ops still going to be used for > > > something? > > > > rx_ opcodes are bro

Re: Call for B0rked

2005-09-13 Thread Matt Diephouse
Leopold Toetsch <[EMAIL PROTECTED]> wrote: > > Also, is rx.ops obsolete? PGE seems to be the new solution. If so, can > > we get rid of rx.ops? Or is rx.ops still going to be used for > > something? > > rx_ opcodes are broken for several reasons: they are non-reentrant due > to the usage of IntSta

Re: Call for B0rked

2005-09-13 Thread Leopold Toetsch
Joshua Hoblitt wrote: Is it just me or is it b0rked to have a file named src/parrot.c that does nothing while the entry point for the parrot executable lives in imcc/main.c? Around 2 years ago test_main.c was Parrot's main and imcc was a standalone PIR->PASM translator. With the integration of

Re: Call for B0rked

2005-09-13 Thread Leopold Toetsch
Matt Diephouse wrote: AFAICT, there's currently no support for: - Lexical/anonymous classes - Submethods Yep. Also, is rx.ops obsolete? PGE seems to be the new solution. If so, can we get rid of rx.ops? Or is rx.ops still going to be used for something? rx_ opcodes are broken for seve

Re: Call for B0rked

2005-09-13 Thread Leopold Toetsch
chromatic wrote: Hi all, In a recent discussion with Chip and Leo, the idea came up to ask for a list of very specific TODO items -- specifically things that should work but don't. Some of the items in this thread are TODOs, some bugs, and some could be noops. I'll try to classify items in

Re: Call for B0rked

2005-09-09 Thread Andy Dougherty
On Fri, 9 Sep 2005, Leopold Toetsch wrote: > Andy Dougherty <[EMAIL PROTECTED]> wrote: > > On Wed, 31 Aug 2005, Chromatic wrote: > > >> Hi all, > >> > >> In a recent discussion with Chip and Leo, the idea came up to ask for a > >> list of very specific TODO items -- specifically things that shoul

Re: Call for B0rked

2005-09-09 Thread Leopold Toetsch
Patrick R. Michaud <[EMAIL PROTECTED]> wrote: > For splitting on regular expressions, PGE can then provide its own > split method or function ^^ Sic. C shouldn't be an opcode at all. It's a library function or more specifically a method inside some namespace. E.g. String.split Ru

Re: Call for B0rked

2005-09-09 Thread Leopold Toetsch
Andy Dougherty <[EMAIL PROTECTED]> wrote: > On Wed, 31 Aug 2005, Chromatic wrote: >> Hi all, >> >> In a recent discussion with Chip and Leo, the idea came up to ask for a >> list of very specific TODO items -- specifically things that should work >> but don't. > It should be possible to Configure

Re: Call for B0rked

2005-09-07 Thread Andy Dougherty
On Wed, 31 Aug 2005, Chromatic wrote: > Hi all, > > In a recent discussion with Chip and Leo, the idea came up to ask for a > list of very specific TODO items -- specifically things that should work > but don't. It should be possible to Configure and build parrot with a compiler other than th

Re: Call for B0rked

2005-09-03 Thread Joshua Hoblitt
During OSCON, over beers with Chip, I made the observation that there is probably a large group of people that would like to contribute a few hours per work to Parrot development but that there are no TODO tasks that can be done reasonable accomplished at that level of commitment. Chip stated that

Re: Call for B0rked

2005-09-03 Thread Joshua Hoblitt
Is it just me or is it b0rked to have a file named src/parrot.c that does nothing while the entry point for the parrot executable lives in imcc/main.c? -J -- On Wed, Aug 31, 2005 at 04:04:45PM -0700, chromatic wrote: > Hi all, > > In a recent discussion with Chip and Leo, the idea came up to ask

Re: Call for B0rked

2005-09-01 Thread Tim Bunce
On Wed, Aug 31, 2005 at 04:04:45PM -0700, chromatic wrote: > Hi all, > > In a recent discussion with Chip and Leo, the idea came up to ask for a > list of very specific TODO items -- specifically things that should work > but don't. Not very specific, but: "whatever Ponie needs most". I'm sure

Re: Call for B0rked

2005-09-01 Thread Patrick R. Michaud
On Wed, Aug 31, 2005 at 07:37:01PM -0400, Will Coleda wrote: > > However, I vote for the following, which are more specific: > > Unfinished Opcodes: > > https://rt.perl.org/rt3//Ticket/Display.html?id=32544 (split) [should > be doable if we s/regexp/perl 6 rule/ and use PGE.] In recent discus

Re: Call for B0rked

2005-08-31 Thread Matt Diephouse
chromatic <[EMAIL PROTECTED]> wrote: > In a recent discussion with Chip and Leo, the idea came up to ask for a > list of very specific TODO items -- specifically things that should work > but don't. AFAICT, there's currently no support for: - Lexical/anonymous classes - Submethods It's possi

Re: Call for B0rked

2005-08-31 Thread Will Coleda
There's a bunch of generic things at: http://rt.perl.org/rt3/NoAuth/ parrot/Overview.html, as well as in docs/ROADMAP However, I vote for the following, which are more specific: Unfinished Opcodes: https://rt.perl.org/rt3//Ticket/Display.html?id=32544 (split) [should be doable if we s/regexp

Call for B0rked

2005-08-31 Thread chromatic
Hi all, In a recent discussion with Chip and Leo, the idea came up to ask for a list of very specific TODO items -- specifically things that should work but don't. We'll gather a list and figure out what's up, whether someone fixed it since then, whether the docs are misleading, or whether it's