j1n3l0

• About: I use Perl ... extensively ;)

Recent Actions

• Commented on What should Rakudo-js aim for first?
  I would say target plain old JS for a start. All the other stuff can/is done in plain old JS :)...
• Commented on Ch-ch-ch-ch-changes
  1 - subroutine signatures ... anything else would require some thought ;)...
• Commented on Subclassing Tricky Non-Moose Classes: Constructor Problems
  oops! here is the example I meant to give above: #!/usr/bin/env perl use strict; use warnings FATAL => 'all'; use Test::Most; { package Animal; sub new { bless [ $_[1] ], $_[0] } sub name { shift->[0] } } subtest...
• Commented on Subclassing Tricky Non-Moose Classes: Constructor Problems
  I often find the the best way to extend a non-moose based object is by delegation: If the non-moose class had sensible defaults you'd normally just need a builder method but as you can see you can initialize it in...
• Commented on What should be core in Perl 5.16?
  Subroutine signatures ... and perhaps multi methods ;)...
• Commented on And suddenly, you're hip
  I like learn you some haskell ;)...
• Commented on So who knew...
  How tidy do you want it? I find Data::Dumper::Concise usually does the right thing....
• Commented on qw() in list context deprecated
  I never actually knew you could do this: for my $i qw[foo] { say $i } If it simplifies the core and is (as it seems) the change I say thank you and good riddance ;)...
• Commented on The face of the CPAN
  The face of CPAN I like to see is search.cpan.org. IMHO it's easily the most useful ;)...
• Commented on On RJBS's automatic version numbering scheme
  Personally, I'm a fan of version numbers that are boring and incremental. As long as I can install a newer version in place of an older version of my modules, and I don't have to think too hard about their...
• Commented on London Perl Workshop 2009
  My apologies for the misspelling, I noticed it after I posted....
• Posted London Perl Workshop 2009 to j1n3l0

  So I finally managed to attend a Perl workshop over the weekend and it was awesome! I saw some excellent talks and even got a goddie bag ... I was not expecting that. Some personal highlights:

  Most entertaining talk
  For me it was Piers Crawleys lightening talk/song …

• Commented on Another reason why I use Emacs as my primary editor
  You may want to check out jrockway's cperl-mode...
• Posted hello world to j1n3l0

  finally got an account set up ;)

  big thanks to everyone who made this site possible ... it's awesome!

  hopefully this means one will be blogging about perl on a regular basis.

Comment Threads

• afoolishmanifesto.com commented on Ch-ch-ch-ch-changes

  Prototypical OO A good REPL CTypes

  (and is anyone ever going to fix this infuriating comment system?!)

• corwin commented on Ch-ch-ch-ch-changes
  • strict (vars at least) and warnings by default

  Honestly, can't come up with two more without reading up or thinking about it, I'll do both and come back.

  Okay,

  • try::tiny in core would be nice

  That's all I got.

• leonerd commented on Ch-ch-ch-ch-changes

  Almost everyone here is adding the same predictable things... "real" OO, without defining what that means, and function/method prototypes/signatures, as a way of unpacking arguments. That's not what I'd like to see.

  What I'd like to see is the idea started by the pluggable keywords API, extended a lot more. Create a mechanism for pluggable keywords to be invoked, not at the surface characters of the syntax of a perl source-code file, but at strategic points in the parse tree of a perl program.

  I'd like to see optrees expressable as Perl-accessible object state, in ways that c…

• David Cantrell commented on Ch-ch-ch-ch-changes

  1. LISP-stylee macros.

  2. Ability to have multiple versions of modules installed.

  3. A text/character encoding system that doesn't confuse the hell out of me.

• Vladimir Melnik commented on Subclassing Tricky Non-Moose Classes: Constructor Problems

  Thank you!

  In my case, subclassing a ResultSet of DBIx::Class has been solved by the following couple of subs:

  # Sometimes DBIx::Class has to create an object based on a ResultSet's
  # class. In several cases (for example, see the as_subselect_rs() method
  # of DBIx::Class::ResultSet) it invokes the constructor with a single
  # parameter (a DBIx::Class::ResultSource::Table-based object), which Moose
  # doesn't like.
  
  sub FOREIGNBUILDARGS {
  
      my $class = shift;
  
      if( (scalar(@_) eq 1) && (UNIVERSAL::can($_[0], 'isa')) ) {
  
          return({ _result_source…