The first contains initialization data (from a config-file), the second is build from this data, let's say a pathname.

If it's built from the data, why have an attribute for it? Is it a very expensive calculation?

Reading Moose::Manual::Construction it seems that you could write a BUILDARGS sub that generates the second attribute based on the first one. Then Moose's internal mechanisms set the ro attributes, you don't have to do it.

Finally, in my limited understanding "ro" just means that no public accessor for changing the object is created - you can still change it through $self->{yourattribute} = $new_value inside the class.

Perl 6 - second systems done right

In reply to Re: Moose and BUILD and 'ro' attributes by moritz
in thread Moose and BUILD and 'ro' attributes by Brutha

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.