Honestly, please feel free to tell me off for using SmartAss mode but I can't resist to make two comments :->

  1. Using Moose for a class that has attribute's you can't declare the Moose way sort of defeats the purpose of using Moose in the first place, doesn't it? Maybe you are better off doing this the "classical" way.
  2. Is it possible that these classes need to be re-designed? If you have more atributes than you can manage/declare then there might be something wrong with it. I don't claim to be a master OO designer at all but others here certainly are and it might be worth posting your design here to get some advice from other monks.
    My question would be, if this class has hundreds of attributes (or more?) then what does the API look like? How would you document it?

As for the attribute list: I think the behaviour that you are seeing makes sense. Yes, the parent's BUILD method is called but $self isa "Child", so $self->meta->get_attribute_list should return the Child classes attribute list as far as I can see.

In reply to Re^3: Problem generating builder functions with Moose for inherited objects by tospo
in thread Problem generating builder functions with Moose for inherited objects by Neighbour

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.