Re^4: Why Perl 6 is taking so !@#$ long

The requirement that says "Must run on every OS known to Man, and then some." Writing C that's that portable is hard, but I don't think I need to tell you that. One of the features I haven't mentioned is PGE, which is, essentially, the parser. Patrick Michaud is currently writing it in PIR. Who's going to write it in C? I don't know enough portable C to do so ... finding someone who knows enough, has the time, and is interested is going to be a ... challenge.

My criteria for good software:

Does it work?
Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

Comment on Re^4: Why Perl 6 is taking so !@#$ long

Replies are listed 'Best First'.
Re^5: Why Perl 6 is taking so !@#$ long by duff (Parson) on Feb 28, 2006 at 15:41 UTC
Patrick's original implementation of PGE was in C. Now that he's got a nifty PIR implementation, it shouldn't be too much work for him to create a C implementation again if the need arises. As I understand it, the main problem is that the PIR implementation utilizes continuations quite a bit, so those would have to be "ported" to C as well to keep the implementation simple yet equally as powerful. duff	[reply]

Replies are listed 'Best First'.

Re^5: Why Perl 6 is taking so !@#$ long
by duff (Parson) on Feb 28, 2006 at 15:41 UTC

Patrick's original implementation of PGE was in C. Now that he's got a nifty PIR implementation, it shouldn't be too much work for him to create a C implementation again if the need arises. As I understand it, the main problem is that the PIR implementation utilizes continuations quite a bit, so those would have to be "ported" to C as well to keep the implementation simple yet equally as powerful.

duff

[reply]