Re^4: Stop Using Perl

> Try Moose attribute initializers, especially if you use grouping parentheses.

An example would have been nice ...

(... google ... google...)

I think you mean something like

    has pizza => (
        is     => 'ro',
        isa    => 'Pizza',
        writer => '_pizza',
    );
[download]

which is just syntactic sugar (sic) for

    has 'pizza' , 
        is     => 'ro',
        isa    => 'Pizza',
        writer => '_pizza',
    ;
[download]

and maybe should have been better designed as

    has pizza => {
        is     => 'ro',
        isa    => 'Pizza',
        writer => '_pizza',
    };
[download]

Cheers Rolf

_{(addicted to the Perl Programming Language and ☆☆☆☆ :)}

Comment on Re^4: Stop Using Perl Select or Download Code

Replies are listed 'Best First'.
Re^5: Stop Using Perl by LanX (Saint) on Jan 02, 2015 at 02:02 UTC
update FWIW: a new `feature` allowing to change `=>` from "fat comma" to a kind of "pair operator" wouldn't effect Moose's `has()` w/o parens. `DB<105> sub has { \@_} DB<106> has pizza => scalar is => scalar 'ro' => ["pizza", "is", "ro"]` [download] It's `scalar(CODE)` which enforces a scalar comma within CODE to only return the last element. `DB<107> has pizza => scalar ( is => scalar 'ro', ); => ["pizza", "ro"]` [download] OTOH a changed `=>` doesn't necessarily need to act like a scalar comma. Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :)}	[reply] [d/l] [select]
Re^6: Stop Using Perl by Anonymous Monk on Jan 02, 2015 at 07:50 UTC
In other words, fat comma and regular comma would behave differently with regard to parens. No thanks.	[reply]