On Wed, 21 Aug 2002, Melvin Smith wrote: > At 07:00 PM 8/21/2002 -0400, 'John Porter' wrote: > >No; but statements like "imcc MUST provide access to ALL of parrot's > >(still very dynamic) feature set" and discussions of imcc syntax > >naturally lead to questions of imcc's role in the parrot project. > >E.g. "will the perl6 compiler target imcc?" > > Good question. The problem is, there is no one but us to answer > that question. Or who are we waiting for? I can see a need for either an "IMCC quick mode" or a way for the compiler to bypass IMCC when handling things like evals and one-liners, where startup time dominates. However, if we already have a working register allocator and peephole optimizer, I see little reason to write another. > >While imcc is cool and worthy, it probably oughtn't be discussed on > >this list untless/until it is a "blessed" member of the parrot suite. As opposed to the blessed BASIC and Befunge? I personally don't see that there's enough traffic to justify a separate parrot-languages list. For the time being, p6i and p6l seem to divide things up enough (maybe too much, given how many things are cross-posted, and how many people are subscribed to both). /s