sillymoos

• Website: perltricks.com
• About: I run perltricks.com and write most web-related Perl code.

Recent Actions

• Commented on Perl Exercism
  Hey Gabor, This looks really interesting, thanks posting!...
• Commented on MooseStyle: Self-made inline vs cpan-based inline
  nice!...
• Commented on MooseStyle: Self-made inline vs cpan-based inline
  Hey Matthias, Thanks for considering the article even worth discussing :) I'll check out Mo::Inline. One thing I wanted to clarify: generally I would advocate using Moo/Moose over vanilla Perl OO, but there seems to be a lot of interest...

Comment Threads

• Matthias commented on MooseStyle: Self-made inline vs cpan-based inline

  I would has discussed it there, but your blog has no comment system.

  It's just bugging me that something so simple has so many hackish homebrew solutions.

  I know TMTOWTDI but sometimes I wish me more common solutions. And Mo::Inline had looked like a good compromise. At least for me.

• Toby Inkster commented on MooseStyle: Self-made inline vs cpan-based inline

  Or in Moose/Moo:

  has [qw/x y/] => ( is => 'rw' );
  

• Tom Molesworth commented on MooseStyle: Self-made inline vs cpan-based inline

  An upgrade to Mo::Inline appears to be behind this issue for YAML:

  https://rt.cpan.org/Ticket/Display.html?id=90817

  and I think a similar issue was behind this:

  https://rt.cpan.org/Ticket/Display.html?id=76664

  It's not the most pleasant code to be debugging either.

  It's an interesting idea, but I'm treating it as a warning sign in code in future, particularly anything that so many other modules depend on.

• Matthias commented on MooseStyle: Self-made inline vs cpan-based inline

  Is your issue about Mo or about non-core dependencies?

  At least Mo::Inline can update all your scripts with one command.
  

  
  
  mo-inline lib/
  
  # or mo-inline ./ or what ever
  
  
  Something that I am missing on my self made Accessors.
  
  ... 
  
  under the assumption that the bug has been fixed and the latest version
  
  of Mo is installed on the development computer. ;-)
  
  

• Tom Molesworth commented on MooseStyle: Self-made inline vs cpan-based inline

  > Is your issue about Mo or about non-core dependencies?

  Neither - it's about modules which use Mo::Inline. Mo itself seems fine, if a module uses it and works, that's great. Non-core dependencies... the more the merrier. I have no objections to a module depending on Mo itself. My specific complaint (as Mithaldu was asking) is that debugging something which has been through the Mo::Inline process is a headache I'd rather avoid.

  Granted, YAML is perhaps an extreme case, several things depend on it so breakage is very visible, and it's mildly disheartening to open the RT que…