On 23 January 2013 18:55, Jonathan Swartz <swa...@pobox.com> wrote:
> Yes, the solution for this is for Poet and Mason to use namespace::auto
> clean or similar to remove the Mooseisms from their namespaces after
> compilation.
>
Ah, yes, am so used to autoclean being part of every Moose class I write
that I hadn’t even noticed it was missing from Poet and Mason.
Probably worth adding __PACKAGE__->meta->make_immutable; to (most?) of the
classes as well [1], if anybody fancies going through the sources and
testing that it doesn't break anything. The namespace::autoclean change
should be safe but I am not sure about make_immutable.
>
> Jon
>
>
Thank you Jon.
Allan
[1]
http://search.cpan.org/~doy/Moose-2.0604/lib/Moose/Manual/BestPractices.pod#namespace::autoclean_and_immutabilize
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Mason-users mailing list
Mason-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mason-users
