On Thu, Nov 12, 2009 at 12:13:29AM +0000, Ian Sillitoe wrote: > 2009/11/11 Stevan Little <stevan.lit...@iinteractive.com> > > > > > I was passing a string as an argument to the 'first' delegation method and > > not a code ref (which is what first expects). > > > > > Groan... yup this was it - you're a star, many thanks. > > Seems my error came from rushing from 'find' (as in MX::AttributeHelpers) to > 'first' (M::M::Attribute::Native) without properly thinking about what I was > doing. I'm so used to Moose providing me with useful errors I got completely > thrown by the seg fault (excuse the pun). > > The usage is perfectly clear in the docs for M::M::Attribute::Native (in > fact - while I'm here - the docs have improved massively, many thanks to > those involved). I was just being a moron. > > Having said that - segfaulting does seem pretty unfriendly behaviour - > especially from such a core module. Seeing a prototype error rather than > segfault would certainly have saved me a great deal of time (and more > importantly - stopped me from bothering you guys). Let me know if you want > me to write it up as a bug report, doc patch, etc
I just fixed this in Moose to no longer bypass the prototype like that, and submitted a bug report for List::Util... hopefully this should all be dealt with shortly(: -doy
