Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?

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

by dragonchild (Archbishop)
on Feb 28, 2006 at 15:35 UTC ( #533381=note: print w/replies, xml ) Need Help??

in reply to Re^3: Why Perl 6 is taking so !@#$ long
in thread 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:
  1. Does it work?
  2. 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.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://533381]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (3)
As of 2018-02-19 14:45 GMT
Find Nodes?
    Voting Booth?
    When it is dark outside I am happiest to see ...

    Results (265 votes). Check out past polls.