NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
forking the world again? (Score:5, Interesting)
I mean, it's the nature of things to change, but we're not going to win over converts from other languages if they have to learn all new regex syntax to use perl 6.
Re:forking the world again? (Score:2, Insightful)
Note that the new syntax is also there to allow more powerful, BNF-like, constructs.
Re:forking the world again? (Score:2)
Yes, but if all those millions of young'ns out there that only know java, and are just now learning the wonders of regexps read about "Perl regular expressions" in their javadocs, and then try to use perl6 and discover that the syntax has completely changed, they aren't going to be eager to figure it out.
Note that the new syntax is also there to allow more powerful, BNF-like, constructs.
Don't get me wrong, I'd love if if Perl made it trivial to write a parser for a BNF expressable grammer, but wouldn't that functionality be better left to a module (Parse::BNF sounds like a great name) with methods for defining grammers using hashes of hashes of arrays of hashes of tokens => subs?
I mean, consider how many people use regexps on a daily basis to how many would even want to use BNF grammers on a weekly basis.
Reply to This
Parent
Re:forking the world again? (Score:3, Interesting)
They'll cope. :)
The current regex syntax is past the point where adding new syntax is conceptually feasable.
Also, if you rea
Recursive regexes (Score:1)