News for hackers. Stuff that matters.
Re:“2015 will be the year that Perl 6 officially launches fo... by tormeh on Friday November 07, 2014 @06:25AM (#8572026)
What's supposed to be so great about Perl 6? I associate Perl with inscrutable cat-walked-on-the-keyboard programs and little else. Can someone in the know explain?
Re:“2015 will be the year that Perl 6 officially launches fo... by lmm on Friday November 07, 2014 @06:54AM (#8572098)
Perl was, in its day, a breath of fresh air. It had an emphasis on practicality that made easy things very easy: regex literals, default arguments like $_, minimal syntax overhead, with things that would be syntax in other languages hoisted to interpreter args (-e, that arg that means "run this as an awk-style loop"), and so on. More than that, the project worked as a holistic ecosystem, rather than just a language and some tools: these days every language has something like CPAN, but it was a huge innovation at the time. Perl also pioneered a lot of the unit-testing infrastructure that we take for granted these days; every project in CPAN was expected to have tests, using the same libraries, and they ran as part of the install process. A cynic might say that perl innovated here out of necessity; lacking static typing and not having VM isolation means good unit tests are a necessity. But still, the resulting infrastructure is very good, and some very solid programs are written in perl. In many ways I'd say it was the go of its day.

The downside of the emphasis on practicality was that the language always suffered from incoherence; with no principled foundation it's been slow to adapt as the practical things users want to do change (e.g. I'd argue string manipulation is a lot less important than it used to be - if you were writing perl today, you might give json manipulation the same prominence as regexes). Perl 6 may have been an effort to fix this, but went too far in the opposite direction; overly formalized, with a premature separation between VM and language that massively slowed development.

There's a lot of good stuff about modern perl - Moose and the like - but IMO it's too little, too late; other languages have been able to improve their infrastructure to (mostly) match perl for easy things. Meanwhile perl's incoherence makes it very hard to write large programs and solve hard problems, where languages with a firmer theoretical foundation and stronger stylistic principles have a huge advantage.

Re:“2015 will be the year that Perl 6 officially launches fo... by mst on Friday November 07, 2014 @07:43AM (#8572234)
Every time I try to write ruby or python code, as soon as I need to write classes I realise just how much boilerplate they require compared to Moose and how depressing not having first-class attributes, method modifiers and roles is, and end up back writing perl5.
Re:“2015 will be the year that Perl 6 officially launches fo... by fennecfoxen on Friday November 07, 2014 @08:01AM (#8572297)
As someone who has written both Perl and Ruby (in that order), you might be interested in this Ruby gem to alleviate at least some of those problems: https://github.com/solnic/virtus
Re:“2015 will be the year that Perl 6 officially launches fo... by Diederich on Friday November 07, 2014 @07:49PM (#8575516)
This is a thoughtful post, thank you.

> Meanwhile perl's incoherence makes it very hard to write large programs and solve hard problems ...

I've been on teams writing very large systems solving very hard problems in Perl 5 for more than 20 years. I know that some of that stuff that was written in the 90s is still under active development and maintenance today, even though it's several developer generations in the past.

Perl 5 may or may not be 'incoherent'. It is certainly somewhat idiosyncratic. But so is JavaScript, perhaps to a lesser degree.

Perl 5 in the large requires some somewhat different (but not too difficult) disciplines.

But that's not so different than most other languages.

> In many ways I'd say it was the go of its day.

This made me smile! Thank you again.

Re:“2015 will be the year that Perl 6 officially launches fo... by lmm on Saturday November 08, 2014 @04:22AM (#8576425)
> Perl 5 may or may not be 'incoherent'. It is certainly somewhat idiosyncratic. But so is JavaScript, perhaps to a lesser degree.

I think if "it's not a lot worse than Javascript" is the best you can say in its favour...

> Perl 5 in the large requires some somewhat different (but not too difficult) disciplines. But that's not so different than most other languages.

The problem I always saw was that libraries would follow their own styles, so once you had a project that depended closely on several different libraries you'd be forced to cut against the grain of several of them. It's a problem that's lessened in a language with a single standard way of doing OO, a single standard way to do event-driven I/O, or even trivial things like code formatting. Maybe the perl community has found more of a consensus in recent years.

Nowadays I work almost completely in scala, which some people compare to perl, so I'm concerned about not repeating perl's decline in popularity.

Re:“2015 will be the year that Perl 6 officially launches fo... by raiph on Sunday November 09, 2014 @11:55AM (#8580233)
> The problem I always saw was that libraries would follow their own styles, so once you had a project that depended closely on several different libraries you'd be forced to cut against the grain of several of them. It's a problem that's lessened in a language with a single standard way of doing OO, a single standard way to do event-driven I/O, or even trivial things like code formatting.

The Perl 6 language design directly addresses this problem. The intent is to avoid throwing out the baby (making both timtowtdi and long term language evolution practical) with the bath water (lack of composability of the various ways to do things and of new features that emerge). The Rakudo implementation is most of the way there.

Re:“2015 will be the year that Perl 6 officially launches fo... by GregBuchholz on Friday November 07, 2014 @04:19PM (#8574672)
I think the impact of Perl is even bigger than what you are describing. I kind of see Perl as the first language which finally lead the masses out of the wilderness-of-C, and brought forth the light of reference-counting/garbage-collection (no more manual memory management and segfaults), dynamic typing, and "advanced" data structures like hashes/dictionaries (no more off-by-one errors, no more buggy reimplementations with pointer chasing). And actual honest-to-goodness strings, not null-terminated abominations. All without out a syntax that was too scary or unfamiliar. In the 90's Perl was the gateway drug to the more lispy future that we now inhabit.
Re:“2015 will be the year that Perl 6 officially launches fo... by Roboprog on Saturday November 08, 2014 @12:39AM (#8576144)
I like that Perl 5 uses reference counting instead of a full-blown GC and that small scripts start up quickly with a small memory footprint. Alas, Perl 6 went down the garbage collecting virtual machine path, at which point, it has to catch up with Java while trying to differentiate itself from it.
Re:“2015 will be the year that Perl 6 officially launches fo... by raiph on Saturday November 08, 2014 @01:01AM (#8576179)
What startup delay and RAM usage do you think is just too large to be acceptable for a small script, no matter how good a language/compiler is in other respects?
Re:“2015 will be the year that Perl 6 officially launches fo... by Roboprog on Saturday November 08, 2014 @02:30PM (#8577897)
Good question, and I'm not even sure. Perl 5 on my Mac is about 1.2 MB resident to run a one-liner, though, and I'm pretty sure I can't load the JVM in 1 or 2 MB. Need to follow up on that to find smallest practical Java program (as a contrast)

Similarly (same laptop), I can get perl to print its version (5.16.2) in about 0.01 secs (2nd time), but java (1.8.0_11-b12) takes about 0.11 secs (2nd time).

Most of my work is in Java, but it gets to be a tyrannical hammer that must be used for everything in some minds :-(

Again: Parrot having to compete with the JVM makes me sad.

Re:“2015 will be the year that Perl 6 officially launches fo... by raiph on Sunday November 09, 2014 @08:47AM (#8579887)
Fwiw most Rakudo devs now prefer MoarVM for most things because it's generally the fastest, leanest, least buggy and most specification compliant of the currently available backends (MoarVM, JVM, Parrot). MoarVM is definitely the right pick for folk who want the leanest startup P6 can deliver.

http://moarvm.org/

Even with the MoarVM backend, Rakudo takes a lot more time and RAM to startup than the compiler for most mainstream languages. It handily beats the JVMs devs use but that's not saying much.

On the third hand, a few devs have said they are regularly using Rakudo at $work, including for one-liners.

If anyone wants to try P6 I recommend RakudoBrew:

https://github.com/tadzik/rakudobrew

Re:“2015 will be the year that Perl 6 officially launches fo... by lmm on Friday November 07, 2014 @05:22PM (#8574976)
Maybe. I think people underestimate the importance of TCL, because it was (relatively) buried so shortly after (mostly for political reasons) - it had a lot of influence on Python in particular. But my perspective is of course coloured by my own experience.
Re:“2015 will be the year that Perl 6 officially launches fo... by raiph on Sunday November 09, 2014 @12:04PM (#8580255)
> Perl 6 may have been an effort to fix this, but went too far in the opposite direction; overly formalized, with a premature separation between VM and language that massively slowed development.

I also think the Parrot VM project added a few years to P6's gestation.

When you say "overly formalized", perhaps you mean the early break out of mailing lists and especially the Parrot project? I don't think "overly formalized" fits the last decade of Perl 6 development -- Pugs (2005 - 2007) was distinctly anarchistic.

Re:“2015 will be the year that Perl 6 officially launches fo... by JohnBooty on Friday November 07, 2014 @08:55AM (#8572467)
I've been farting around the software world for a while (but have never touched Perl) and that's the best explanation of Perl's appeal that I've ever read.
Re:“2015 will be the year that Perl 6 officially launches fo... by huherto on Friday November 07, 2014 @08:43AM (#8572426)
> The downside of the emphasis on practicality was that the language always suffered from incoherence

IMHO, it was coherent. But the syntax is wierd (may be usage of symbols $%@{}[] ) for people unfamiliar with it.

I haven't done big projects with perl in the last 12 years. But when I need it, it is like riding a bike.

Re:“2015 will be the year that Perl 6 officially launches fo... by danielweber on Friday November 07, 2014 @09:30AM (#8572610)
Perl optimized itself to death. They wanted a new feature, realized they could save 3 keystrokes per day by using $‽ for some new feature, all the experts agreed, and they go with it.

I'm really afraid that Rails is going the same way, that the DRY mantra is going to eventually lead to a Huffman encoding only parseable by Rails experts, and then no one new will want to get on board.

Re:“2015 will be the year that Perl 6 officially launches fo... by rlucas on Friday November 07, 2014 @01:31PM (#8573929)
Perl's "magic" variables like "$?" were not named to optimize keystrokes.

Most of Perl 5's syntax comes from well established (for perhaps a decade) UNIX culture, from shell, awk, sed, and C syntax conventions. Vanishingly little is actually novel to Perl.

Rails, which is obviously not a peer to Perl, but which you bring up as "going the same way," does similarly have a huge emphasis on convention. But most of its conventions are de novo, made up within the Rails/Ruby community.

You can hate Perl (5) all you like; no accounting for taste and all. But if you find parts of it unfamiliar, it's probably because you are ignoring (or ignorant of) where it came from.

Re:“2015 will be the year that Perl 6 officially launches fo... by raiph on Sunday November 09, 2014 @08:45PM (#8581650)
Repeat post with better formatting:

Standard Perl 6 has just these non-English variables:

- $_ means "it"

- @_ means "args"

- $! means "current exception/error"

- $/ means "last match"

- $0 means $/[0], the first captured value of the last match

All other system variables have understandable English names, eg:

- $IN means the STDIN object/handle

- $OUT means the STDOUT object/handle

- %ENV means a hash (dict, associative array) of system environment variables

- $PID means the system process id

- $*KERNEL means the operating system kernel running under

Etc.

Re:“2015 will be the year that Perl 6 officially launches fo... by raiph on Sunday November 09, 2014 @11:47AM (#8580213)
Standard Perl 6 has just these non-English variables:

* $_ means "it" * @_ means "args" * $! means "current exception/error" * $/ means "last match" * $0 means $/[0], the first captured value of the last match

All other system variables have understandable English names, eg:

* $IN means the STDIN object/handle $OUT means the STDOUT object/handle %ENV means a hash (dict) of system environment variables $PID means the system process id $*KERNEL means the operating system kernel running under

Etc.

Re:“2015 will be the year that Perl 6 officially launches fo... by treehau5 on Friday November 07, 2014 @09:55AM (#8572737)
Rails is a framework. You can still write Ruby without the cryptic DSLs.
Re:“2015 will be the year that Perl 6 officially launches fo... by danielweber on Friday November 07, 2014 @11:35AM (#8573304)
Yes, I love Ruby, and use it a lot outside of Rails.

I have some issues with Ruby "helpfully" letting you leave out more and more syntax, like parentheses from multi-argument function calls, or saying you don't need {} if the last argument is a hash, which are easy to grok if you already know Ruby but can be yet-another-confusing-rule for newbs. But those are relatively minor.

Re:“2015 will be the year that Perl 6 officially launches fo... by treehau5 on Friday November 07, 2014 @01:55PM (#8574051)
When I first learned ruby, it was my first dynamic language I ever fully experienced. I never found the poetry mode to be an issue, and in fact the community was so new and vibrant, they made it very clear to me what was going on. I believe every ruby tutorial I have ever seen made it very clear what was going on.

as far as the hash, you can always inspect the actual arguments being passed, which doubles as a nice learning exercise for beginners.

Re:“2015 will be the year that Perl 6 officially launches fo... by vithlani on Wednesday November 12, 2014 @06:22AM (#8594912)
Very well put sir, very well put....
Re:“2015 will be the year that Perl 6 officially launches fo... by ohsnap on Friday November 07, 2014 @08:03AM (#8572298)
totally agree. Perl was super innovative in it's day. It's really hard for a language to evolve after it becomes established.
Re:“2015 will be the year that Perl 6 officially launches fo... by raiph on Sunday November 09, 2014 @11:32AM (#8580172)
The Perl 6 design has directly addressed that very problem from the start.

Aiui Larry Wall believes it will be significantly easier for Perl 6 to evolve than for Lisp to do so, without falling in to the Lisp Curse trap.

[deleted]
Re:“2015 will be the year that Perl 6 officially launches fo... by evan_miller on Friday November 07, 2014 @11:18AM (#8573192)
It's actually -ne, perhaps with -a if one wants awk-style field splitting of lines.

-l modifies the output record separator (makes print append \n)

Re:“2015 will be the year that Perl 6 officially launches fo... by bane on Friday November 07, 2014 @09:47AM (#8572686)
Perl is a fundamentally different approach to language design.

It's almost anti-academic in the approach and more linguistic. It's superficially like any other curly braced language but there was lots of thought put into how statements are constructed and making things easy to humans to write rather than for computers to process. So it features all kinds of implicit actions and context sensitive approaches to the language and how it works. It's also an amalgamation of several preceding tools and ideas, and in that sense is almost an "English" of the programming world.

Perl is almost more of a human language than a programming language, and like any other human language, once you learn it and some dialects it makes all kinds of natural sense. Even if you're away from it for a long time it comes back like a second language does and you're up and running really quick. It feels less like programming and more like you're having a conversation with your computer friend.

Even small things that you get used to in Perl turn into huge pains in other languages, things like having regexes be a literal type (rather than trying to shoehorn the syntax into a string like in almost every other language) makes wanting to use them and using them second nature and really natural. Having a state machine you can type up in a few characters and be a first class citizen of the language is incredibly powerful.

Perl 6 is supposed to take these ideas and expand on them, lots of clever new language constructs and first-class grammars are exciting new promising notions. It'll be like going from the language a child speaks to the language an educated adult uses.

I'm concerned Perl 6 has missed it's window, but there's enough interesting stuff going on in the Perl 5 community and there's some really smart people working on it that I'm hopeful it'll be more than another language curiosity.

Re:“2015 will be the year that Perl 6 officially launches fo... by zzzcpan on Friday November 07, 2014 @12:52PM (#8573681)

  > It's almost anti-academic in the approach
I'd say academic approach to programming languages is anti-scientific and therefore anti-academic on itself. They just don't realize it yet.

  > Perl 6 is supposed to take these ideas and 
  > expand on them
The problem is we already have lots of features in Perl 5 that nobody really needs, they just complicate things, raise entry cost, split community, make it impossible to address performance and deployment issues. So, approach on expanding feature set is flawed and frankly always was.

Instead, Perl 7 maybe should get rid of all the unneeded features, restrict feature set, restrict coding conventions, make it easier for newcomers, make it easier for everyone to understand each other's code, make it faster, easy to compile and deploy without having to install interpreter and so on. These issues are much more important, than language features. And yet no one seems to understand that.

Re:“2015 will be the year that Perl 6 officially launches fo... by weinzierl on Saturday November 08, 2014 @02:59PM (#8577976)
I'm curious about the state machine you can type up in a few characters and be a first class citizen. Can you give or link to an example?
Re:“2015 will be the year that Perl 6 officially launches fo... by zzzcpan on Saturday November 08, 2014 @03:07PM (#8578002)
I believe he was talking about regular expressions being first class citizens in Perl:

  ($v1, $v2) =~ /a(b|c)d(e)/;
(regular expressions are state machines)
Re:“2015 will be the year that Perl 6 officially launches fo... by weinzierl on Saturday November 08, 2014 @05:44PM (#8578376)
Ok, I get that. I wrote simple state machines for simple parsing tasks and was just hoping there was an easier way.
Re:“2015 will be the year that Perl 6 officially launches fo... by kbenson on Friday November 14, 2014 @02:11PM (#8608906)
Oh, in Perl 6 there are, grammars[1].

[1]: http://en.wikibooks.org/wiki/Perl_6_Programming/Grammars

Re:“2015 will be the year that Perl 6 officially launches fo... by mike-cardwell on Friday November 07, 2014 @06:40AM (#8572065)

  explicit strong typing
  proper parameter lists
  active metadata on values, variables, subroutines, and types
  declarative classes with strong encapsulation
  roles
  full OO exception handling
  support for the concurrent use of multiple versions of a module
  extensive introspection facilities (including of POD)
  LL and LR grammars (including a built-in grammar for Perl 6 itself)
  subroutine overloading
  multiple dispatch
  named arguments
  a built-in switch statement
  hierarchical construction and destruction
  distributive method dispatch
  method delegation
  named regexes
  overlapping and exhaustive regex matches within a string
  named captures
  parse-tree pruning
  incremental regex matching against input streams
  macros (that are implemented in Perl itself)
  user-definable operators (from the full Unicode set)
  chained comparisons
  a universally accessible aliasing mechanism
  lexical exporting (via a cleaner, declarative syntax)
  multimorphic equality tests
  state variables
  hypothetical variables
  hyperoperators (i.e. vector processing)
  function currying
  junctions (i.e. superpositional values, subroutines, and types)
  coroutines
  lazy lists
  strong module and language versioning
  concurrent object pipes
http://www.perl6.org/archive/faq.html
Re:“2015 will be the year that Perl 6 officially launches fo... by perlgeek on Friday November 07, 2014 @07:26AM (#8572193)
There's a reason this has "archive" in its URL :-)

Rather consult this instead, which is maintained: http://faq.perl6.org/#features

Re:“2015 will be the year that Perl 6 officially launches fo... by tempodox on Friday November 07, 2014 @09:26AM (#8572590)
Is that “perl poetry” or does it mean anything?
Re:“2015 will be the year that Perl 6 officially launches fo... by thristian on Friday November 07, 2014 @06:45AM (#8572080)
I'm not a Perl hacker, but there's one thing that I've wanted a bunch of times in other languages: Perl 6 does for PEGs (Parsing Expression Grammars) what Perl 5 did for regexes: they're part of the core language, you can execute Perl expressions when a PEG rule is matched, that kind of thing.

In Python when I have some data and it grows just a bit too irregular for regexes, I have to start manually writing state-machines or add a dependency on a third-party library and spend an afternoon explaining parsing theory to my co-workers.

Re:“2015 will be the year that Perl 6 officially launches fo... by nly on Friday November 07, 2014 @07:44AM (#8572236)
I want to see Perl 6 push the boundaries but the world isn't quite like it was when Perl 5 made using regex seemless. Competition is much more stiff.

Even in C you can use something like Ian Piumarta's PEG generator[0] that let's you embed semantic actions written in C. For regular grammars, scanners and lexers you have powerful tools like Ragel[1] (which targets 7 languages)

I'm not a Python person, so if the Python libraries proved inadequate I'd probably resort to these tools and then push out a Python module using Cyphon[2].

Personally I'm not a fan of using semantic actions for AST construction. I generally prefer the 'attribute' approach taken by libraries like Spirit (C++) which make the process feel a lot more like deserialization. SAs are still useful however for rejecting or accepting rules based on complex requirements (like "is this IP address routable"?).

[0] http://piumarta.com/software/peg/ [1] http://www.colm.net/open-source/ragel/ [2] http://cython.org/

Re:“2015 will be the year that Perl 6 officially launches fo... by rurban on Friday November 07, 2014 @10:09AM (#8572806)
With perl6 the peg backend is built-in, so you can compile and execute grammars on the fly. A bit like lua's lpeg.

A perl6 Grammar is a first-class object.

Re:“2015 will be the year that Perl 6 officially launches fo... by nly on Friday November 07, 2014 @10:53AM (#8573050)
Sure, but what happens when someone needs something other than PEG/recursive descent, like expression parsing with a custom precedence table? Will Perl6 add that to the core language as well? Where do you draw the line?

LPeg is a library, Spirit X3 (for C++, not yet complete) is a library. Both achieve pretty seamless integration with your code. I think in a library is where this stuff should be.

Re:“2015 will be the year that Perl 6 officially launches fo... by arnsholt on Friday November 07, 2014 @11:48AM (#8573384)
It's pretty easy (to the extent that implementing custom parsing logic is ever easy) to add custom parsing bits to a Perl 6 grammar.

The grammar is just a special class with the rules as methods, so rules with non-standard parsing logic can be implemented using Perl 6 code. Reusing standard rules from custom rules is simply a matter of calling the corresponding method.

The best example of this is probably the EXPR rule in the NQP compiler (which is in turn used by Rakudo's parser), which inserts an operator precedence parser into the recursive descent of the rest of the grammar.

Re:“2015 will be the year that Perl 6 officially launches fo... by oftenwrong on Friday November 07, 2014 @08:10AM (#8572320)
>I associate Perl with inscrutable cat-walked-on-the-keyboard programs and little else.

That's because Perl had a lot of "convenient" shorthand and quirks in the language that could be abused, leading to unreadable, "cat-walked-on-keyboard" code. However, that is just a stereotype. One could also force Perl to straighten its posture with a strict pragma, making much of the eccentricity disappear. I have worked on several large Perl 5 codebases that were/are clean and easy to understand and maintain.

Re:“2015 will be the year that Perl 6 officially launches fo... by bane on Friday November 07, 2014 @09:50AM (#8572700)
Yeah, the default Perl is more of a slang dialect. Lots of implicit assumptions made about you, the language and your job. Once you turn on strict and use some common sense your code reads more like an school essay, but strangely is just about as easy to work in.

Just like real languages have different modes to communicate in, Perl has it's own modes.

I've worked on a couple large-ish Perl codebases too and with some decent code standard found them really easy to work on and extend.

Re:“2015 will be the year that Perl 6 officially launches fo... by raiph on Sunday November 09, 2014 @11:11AM (#8580128)
Perl 6 claims saner defaults. For the strict pragma, it's off by default for one liners and on by default for everything else.

A much bigger relevant change is Perl 6's support for hygienic lexically scoped "slangs". These can be used to relatively cleanly package composable dialects, DSLs, language tweaks etc. Slangs make it practical for a group to establish a default local policy (policies include anything from switching some language tweak on or off to switching to another language entirely) and for an individual programmer to extend or alter that policy in a cooperative manner.

Slangs aren't yet nearly as easy as they supposed to be, but they're getting there. A couple examples are v5 (which switches to another lang entirely) and Tuxic (a tiny idiosyncratic tweak to standard Perl 6):

https://github.com/rakudo-p5/v5/blob/master/README.md

https://github.com/FROGGS/p6-Slang-Tuxic/blob/master/README....

Re:“2015 will be the year that Perl 6 officially launches fo... by Tepix on Friday November 07, 2014 @06:36AM (#8572051)
You may want to read the Apocalypse documents ( http://perl6.org/archive/doc/apocalypse.html ) and the Exegeses ( http://perl6.org/archive/doc/exegesis.html ).

Perl 6 improves upon Perl 5 in countless ways. One of the strongest parts of perl, the regular expressions, have received further improvements. Check out https://en.wikipedia.org/wiki/Perl_6_rules

Finally, if you are familiar with Perl 5, there's special documentation for you at http://perlgeek.de/en/article/5-to-6

Re:“2015 will be the year that Perl 6 officially launches fo... by progman on Friday November 07, 2014 @01:20PM (#8573850)
> One of the strongest parts of perl, the regular expressions ...

... have been copied to Nimrod (now called "Nim") -- even with native C performance and native Perl syntax.

http://nimrod-lang.org/re.html

Perl had its time and lost many of its users (including me) "thanks" to the inacceptable delay. Meanwhile the competitional advantage of Perl 6 is completely gone because many new features have also been implemented in other languages (Rust for instance), even in dinosaurs like Java and C++.

Re:“2015 will be the year that Perl 6 officially launches fo... by raiph on Saturday November 08, 2014 @02:08AM (#8576268)
PCRE wrappers like the module you linked don't give other langs the nice regex integration available in Perl 5, they just give them support for "Perl Compatible Regular Expressions" (hence PCRE), a rough equivalent of P5's regex functionality:

http://en.wikipedia.org/wiki/Perl_Compatible_Regular_Express...

But PCRE is 1990's parsing technology. Who cares if Nim copies parts of P5 regex via PCRE?

The page you linked says "Consider using the pegs module instead.". PEGs, invented in 2004, are more powerful than regex, PCRE ones or otherwise:

http://en.wikipedia.org/wiki/Parsing_expression_grammar

Perl 6 has Perl 6 rules, a unification of PEGs, regex, and lexical closures, built right in to the language. There's nothing like them in Nim, Java, or C++.

http://en.wikipedia.org/wiki/Perl_6_rules

Re:“2015 will be the year that Perl 6 officially launches fo... by progman on Saturday November 08, 2014 @04:03AM (#8576398)
> There's nothing like them in Nim, Java, or C++.

Are you sure?

Nim supports direct access to the AST so macros can be used to define new programming constructs like in Lisp.

Also other languages support things like that (as library), Java for instance:

http://www.antlr.org/

http://tunnelvisionlabs.com/products/demo/antlrworks

Re:“2015 will be the year that Perl 6 officially launches fo... by raiph on Sunday November 09, 2014 @09:43PM (#8581796)
> Nim supports direct access to the AST so macros can be used to define new programming constructs like in Lisp.

Nim macros can't modify Nim's syntax.

That constraint makes perfect sense for Nim but not Perl 6.

> ANTLR

ANTLR has switched from LL(star) parsing to what they call Adaptive LL(star) for v4. P6 Rules have been what Larry has called "LL(star) with kludges" (by which he means the same thing) for about a decade. So ANTLR has caught up with that aspect and indeed ANTLR v4 is nice tech.

But P6 Rules are built in to P6. Its grammar is defined in P6 Rules. User code can modify the language on the fly by modifying the rules. Java (or whatever) + ANTLR is nothing like Perl 6 and Perl 6 Rules.

Re:“2015 will be the year that Perl 6 officially launches fo... by progman on Tuesday November 11, 2014 @08:04AM (#8589573)
> Nim macros can't modify Nim's syntax.

Nim macros can extend Nim's syntax (additional "repeat ... until" for instance). They cannot change the built-in syntax of Nim.

A macro system should never be allowed to change the core syntax of a language because that could lead to very strange errors. If Perl 6 is actually able to do that then it is a dangerous feature.

Re:“2015 will be the year that Perl 6 officially launches fo... by sigzero on Friday November 07, 2014 @09:21AM (#8572562)
The Perl community really frowns upon that kind of code now.
Re:“2015 will be the year that Perl 6 officially launches fo... by JonnieCache on Friday November 07, 2014 @07:19AM (#8572166)
If you've ever enjoyed anything about ruby the chances are that it comes from perl.
Re:“2015 will be the year that Perl 6 officially launches fo... by skywhopper on Friday November 07, 2014 @07:31AM (#8572205)
I'd put it a different way: Ruby stole all the useful syntactic shortcuts from Perl and ignored all the cruft and ugliness.

Unfortunately the one thing Ruby didn't steal from Perl was its speed.

Re:“2015 will be the year that Perl 6 officially launches fo... by sigzero on Friday November 07, 2014 @09:21AM (#8572568)
Hasn't that change in 2.X series?
Re:“2015 will be the year that Perl 6 officially launches fo... by JonnieCache on Friday November 07, 2014 @09:50AM (#8572703)
It's definitely a lot faster. I still wouldn't call it fast.

Of course, most apps are I/O bound, objects in the heap are larger than they appear, blah blah blah.

Re:“2015 will be the year that Perl 6 officially launches fo... by untothebreach on Friday November 07, 2014 @08:12AM (#8572327)
I think most of the good* features of Ruby came from Smalltalk, though you can definitely see the Perl influence.

*at least for my definition of "good"

Re:“2015 will be the year that Perl 6 officially launches fo... by JonnieCache on Friday November 07, 2014 @09:55AM (#8572736)
Indeed the object model is from smalltalk. I don't know why I didnt make that caveat.