Re: Inversed logic when defining which attribute options can be changed

Hi, On Sat, Aug 29, 2009 at 10:28:05PM -0500, Chris Fields wrote: Actually, the 'deny' vs. 'allowed' issue re: legal_options_for_inheritance was brought up in this thread: http://thread.gmane.org/gmane.comp.lang.perl.moose/989/focus=990 Seemed like there was some consensus about using

Exception and attributes

How can I make Mosse throw an user defined Exception (i.E from Exception::Class) when an attribute has a wrong type (or missing, etc) ? Make a new meta class for my attributes , and tell Moose to use that one ? Regards Rolf Schaufelberger

Re: Coercion problem

Hans Dieter Pearcey wrote: Hi Hans, Thanks for your quick reply. I followed your recommendations and used MX::Types::Structured and 'Dict'. However, I get an error when I am calling my constructor -new() : Attribute (cut_types) does not pass the type constraint because: Validation failed for

Re: Coercion problem

Excerpts from Emmanuel Quevillon's message of Wed Sep 02 10:47:06 -0400 2009: Attribute (cut_types) does not pass the type constraint because: Validation failed for 'ValidCutTypes' failed with value { blunt = [ blunt ] } at lib/Bio/Restriction/Analysis/FrameCutters.pm line 315 where as it is

attribute_helpers merged

As far as I can tell we weren't waiting for anything else to be done, so I've merged to master and pushed. Can we do a dev release today? hdp.