I find it somewhat scary that MooseX seems to be messing with some pretty standard Perl magic. I don't think I've ever seen odd nonstandard behavior from regex captures like that before.
I did notice that the value suddenly shifted to the 'coerce' string. In my more complicated code this is pulled from, I actually saw 'is_subtype_of'. So there's definitely something strange going on in the background. I'm hoping a guru can shed some light on it. I don't like wierd voodo stuff going on that I can't figure out.
When you say that you don't recommend the numbered capture globals, do you mean in general or specifically when dealing with MooseX? Do you always use your own variables for regex captures? Why? Not being critical, I just like learning and I'm still firmly an early intermediate Perl programmer (by my own guesstimate).
In reply to Re^2: a MooseX Q that's driving me up the wall :)
by tj_thompson
in thread a MooseX Q that's driving me up the wall :)
by tj_thompson
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |