in reply to Re^2: Exporting constants from a Moo role
in thread Exporting constants from a Moo role

Thanks Toby! init_arg => undef is a new one on me. Why do you need to declare a default value (or what is the point) when you use that parameter to the attribute?

I quite often use simple subs for constants if only because the syntax to declare them is simpler and shorter. I guess the author of this code (which is used to access the elements of a work queue job) prioritized simpler and shorter syntax at the calling end, preferring $self->job->[INDEX_FOO] to $self->job->[ $self->INDEX_FOO ] ...

I think I like the solution you showed in your other reply. Thanks again!


The way forward always starts with a minimal test.

Replies are listed 'Best First'.
Re^4: Exporting constants from a Moo role
by tobyink (Canon) on Aug 03, 2018 at 11:49 UTC

    init_arg is used to tell Moo what key will get passed to the constructor for that attribute.

    use v5.16;

package Person {
   use Moo;
   has "nick-name" => (
      is       => "ro",
      init_arg => "nick",
      reader   => "nick_name",
   );
};

my $robert = Person->new(nick => "Bob");     # init_arg
say $robert->nick_name;                      # reader
say $robert->{"nick-name"};                  # attribute name (direct 
+hashref access)

    [download]

    Setting init_arg to undef means that the attribute cannot be passed to the constructor at all. (And if the attribute is also read-only, so there's no writer method, you should probably be setting a default for the attribute too!)

    (And this is not Moo-specific. Moose and Mouse have the exact same features.)

    toby döt ink
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom