When I move the ThreeD::Model package definition to the top of the script, I'm getting a different error: 
Attribute (active_entities) does not pass the type constraint because:
+ Validation failed for 'Entities' with value ThreeD::Entities=HASH(0x
+6011b0a80) at constructor ThreeD::Model::new ...

[download]

So, I changed the constraint to 

   has 'active_entities' => (isa => 'ThreeD::Entities',

[download]

and...

No more errors! (The output is still different, as it says DEBUG 2b, not 2a.)

Update: Why does it work? has is a Perl subroutine, it doesn't run at compile time. You need to actually run the code at runtime for it to have effect. 

($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,

[download]

In reply to Re: Moose class not being constructed by choroba
in thread Moose class not being constructed by SwaJime

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.