News for hackers. Stuff that matters.
Re:Why Did I Choose Perl When Building Crowdtilt? by rb2k_ on Friday August 31, 2012 @07:45PM (#4462174)
What does Perl have in that regard that Ruby hasn't? Ruby also has open classes and you can chain and modify any of the base classes, be it "String" or "Object".

I don't know anything like "MooseX", but that might be because Ruby actually has a somewhat working object system.

Re:Why Did I Choose Perl When Building Crowdtilt? by chromatic on Friday August 31, 2012 @07:54PM (#4462190)
Perl lets you add new language keywords which take effect during the parse phase.
Re:Why Did I Choose Perl When Building Crowdtilt? by klibertp on Friday August 31, 2012 @10:34PM (#4462493)
So, basically, Perl has macros? REAL macros? Like, say, in Lisps? Could I, for example, make fully inlined merge sort, as demonstrated a couple days ago here by a post from Racket blog? Now I'm curious.
Re:Why Did I Choose Perl When Building Crowdtilt? by btilly on Saturday September 01, 2012 @12:40AM (#4462670)
Sort of. Perl has support for something like reader macros. See http://search.cpan.org/~zefram/Devel-Declare-0.006011/lib/De... for details.

One could, in theory, build something like Lisp macros using it, but I don't think that anyone has.

Re:Why Did I Choose Perl When Building Crowdtilt? by chromatic on Saturday September 01, 2012 @01:28AM (#4462739)
Perl 5's parser manipulation doesn't go as far as manipulating an AST, yet. I would like that, but Lisps still have a strong advantage there.