> > On Tue, Sep 12, 2000 at 03:17:47PM -0400, Ken Fox wrote:
> > > That's fine for the VM and the support libraries, but I'd *really*
> > > like to see the parser/front-end in Perl. There are dozens of RFCs
> > > that require some non-trivial extensions to the parser. It would
> > > be nice to code these in Perl
> >
> > Are there any better reasons than "It would be nice?"
>
> Can there *be* a better reason than "It would be nice"? Seriously,
> niceness is a damned fine goal.
One good reason I preffer and I think many other want to do everything in
PERL only, rather than use Perl and C to do the job. ;"). If we have
lex/parser/front-end which can change its behavior trought Perl code then :
1. the transformation of the PerlX --> Perl6 can be done on the fly. Every
Perl hacker can change this behaviour if there is some incompatibility i.e.
more people will work for compatibility.
2. Can mimic other languages easly ... the benefit is that any change to the
language can be tested much more before it is integrated in the core and
from much more people.
3. One very cool idea - make Limited Natural language front-end for very
newscomers
4. Make different "preprocessing schemes" i.e. C like #includes, #define's,
m4 like macros .... etc.... out of core.
5. Make one your very own Perl ;")
6. Make all HTML/XML translators works like they are Perl programs. i.e.
perl blah.xml
7. Make a Debugger
8. Make a profiler
....
Think a litle bit what is the Perl language it is the translator to machine
code ;"), if we can change the translator behavior with such fast
prototyping language like Perl itself there is enormous posibilities...
=====
iVAN
[EMAIL PROTECTED]
=====
