use Perl

• Moose tries to play well (Score:1)

  by Stevan (6065)

  I agree, no module has specific domain over &meta, I am not sure why "other" got so upset.

  I dont know about the other &meta out there, but with Moose we try to always make sure we don't step on other modules toes. And in many cases we avoid calling ->meta and instead fetch the metaclass from the Class::MOP cache in a more direct fashion.

  In fact, Class::MOP (the metaclass system Moose is built on) never insists on &meta and always fetches the metaclass from the cache.

  - Stevan
• use metaclass is not your friend (Score:1)

  by Stevan (6065)

  If the two need to merge in the future, I surmise that:

  use metaclass 'MySpecialMetaClass';

  is my friend.

  This will not work as you think, metaclass.pm installs it as &meta too (just like Moose). But we can talk more about the best solution when you get there :)

  - Stevan
• Me too (Score:1)

  by Alias (5735)

  I always used ->Info in my codegen system's metadata stuff (I was using a rule where any capitalized methods would guarantee to work and never return undef or throw an exception.
  
  But as I look at moving parts of it to CPAN, I most likely would be using ->meta as well.