|
このページは大阪弁化フィルタによって翻訳生成されたんですわ。 |
I understand why you want to use Perl to write Perl. But that's not the only path to "Christmas", and frankly, perhaps not even the most promising one (initially). Also, a non-bootstrapped implementation could be useful in either case, so why is there no alternative project to write a straight-forward interpreter in plain ANSI C? That's what Lua did; making especially sure that compiling Lua is as simple as "gcc *.c". And look at how popular it is, despite being such a poor language.
— monomorph, [Perl 6] Thoughts
One of the goals of Perl 6 is to create a family of languages through lexical grammar modifications. That is, programmers should be able to create their own local (and encapsulated) Perl 6 dialects by modifying the Perl 6 grammar by writing Perl 6 code.
"Adding new lists of things [to remember] to a language is only a good idea if you're making money with certification." -- Juerd Waalboer, on why your program shouldn't have to plead to use new functionality.
Escalation wars... you just have to love'em.
First, David came up with the über-cool CPAN deps page.
Then Andy comes up with a nifty Greasemonkey script to add it to the CPAN distributions main pages.
Then I add a small patch to the script to retrieve some information from the Deps page.
Then David creates an xml interface to CPAN deps, opening the door wide open for Web 2.0 goodiness.
Then (and this is where we are right now) I hack together a new CPAN_Dependencies monkeyscript to take advantage of said xml interface.
This, of course, is nowhere near the end of the story. My new script only scratches the surface of what can be done with the information contained in the xml. As soon as I have some tuits, I'll probably add a way to toggle between showing only the first-level dependencies and all dependencies, and have dependencies color-coded by degree of b0rkage, and whatever bell or whistle I can think of in the meantime.
In $foo #5: