> > Having the minutia of the programmatic run-time state of the parse then > influence the parse itself, is at the heart of the perl5 phenomenon "only > Perl can parse perl"
I don't mean to be hostile, but you're demonstrably wrong, here. (also it's "only perl can parse Perl" as in, only the "perl" implementation can parse the Perl language). There are currently about 2.5 implementations of Perl 6, and while you could backhandedly claim that only Perl 6 can parse Perl 6 (because it's specced as a self-hosting language whose spec is actually written in Perl 6), the reality is that the parts that aren't written in Perl 6 can be written in just about anything (with C/MoarVM and JVM implementations working just fine). It's not a context sensitive grammar that was the issue with Perl 5, it was the lack of a specification outside of the primary implementation. Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com Toolsmith, developer, gamer and life-long student. On Tue, Sep 13, 2016 at 10:35 AM, Bennett Todd <bennett.e.t...@gmail.com> wrote: > Having the minutia of the programmatic run-time state of the parse then > influence the parse itself, is at the heart of the perl5 phenomenon "only > Perl can parse perl", which I rather hope isn't going to be preserved in > perl6. >
