Live data from Hacker News

The Joy of Perl (1998)

salon.com

81–82 of 82 posts

Re: The Joy of Perl (1998)

#81
post #68
post #63

Earlier quoted context omitted.

> There’s no real AST Perl cannot be statically parsed! > Theorem: Parsing Perl 5 is Undecidable https://www.perlmonks.org/index.pl?node_id=663393

> Perl cannot be statically parsed! My usage (modifying syntax / extending the compiler when running Perl programs) doesn't need static parsing. What I need is a way to leverage the existing infrastructure in the interpreter for parsing in a way that's compatible with most modules/usages. AFAIK the parser in perl goes directly from source to an OP tree (modulo running other Perl code on the go that modifies the parsi…

Haha, my comment was definitely tongue in cheek ;) I fully expect most of properly written Perl code to be statically parseable into an AST, save for pathological cases (and I fully expect a proper rubocop-like Perl linter to highlight such ambiguities, and would reject them in any sensible project)

Re: The Joy of Perl (1998)

#82
post #80
post #67

Earlier quoted context omitted.

Too bad. And now it is too late, because Perl 6 has been renamed to Raku ( https://raku.org using the #rakulang tag on social media). Which features would convince you to install Raku?

Which does it offer that are not covered by ruby, python or CL? I am fluent in a lot of languages and cannot really imagine anything that could motivate me to upgrade my perl5 black belt to perl6 except for a well-paid gig that requires it.

Better Unicode support and async/parallel processing primitives that don't depend on a GIL, are the first things that come up.
Post reply on HN