Hey, great! Glad I could help!

Thanks, barefootcoder, I didn't know about Method::Signatures::Modifiers! If we change the Str to String in the signature in the MooseX::Declare example above, we get 'String' could not be parsed to a type constraint - maybe you need to pre-declare the type with class_type at reader Parse::Method::Signatures::TypeConstraint::tc (defined at /home/tim/.plenv/versions/5.18.1/lib/perl5/site_perl/5.18.1/ Parse/Method/Signatures/TypeConstraint.pm line 20) line 7. which isn't terribly helpful. But when we add use Method::Signatures::Modifiers, we get 15 Hello from myDerivedClass In call to myBaseClass::doMsg(), the type String is unrecognized (perhaps you forgot to load it?) at ./useMethodSignaturesModifiers.pl line 20. which tells us exactly what is wrong. Nice! Moops fares no better than unassisted MooseX::Declare here 43 Hello from myDerivedClass In method doMsg: parameter 1 ($m): value "DC Very nice! How much RAM is Eclipse using?" did not pass type constraint (not isa String) at ./useMoops.pl line 48. Neither line 48 nor line 43 have much to do with our code. To be fair to Stevan, when I asked what was wrong with MooseX::Declare, his very sensible answer ended with something like, "but if it's working for you, keep using it."

Mea culpa! I added Class::Tiny above. We need a more complicated example to explore the differences between all of these systems. As has been pointed out, I've got read-only accessors in some and read-write in others. Nonetheless, it's still kind of neat to have them all laid like this.

I agree. That's why I think this is related to the other discussions about CPAN and not just a post about a bug in Config::Simple. Here is a case where it's not experimental code on github and polished code on CPAN, but tarnished code on CPAN and a corrected version on github. We seem to have someone willing and able to correct the bug, but we are unable to correct the bug on CPAN without cooperation from the maintainer. I also agree about the File::Temp warning. Leaving the temporary directory upon successful install seems to both silence the error and remove the directory.

I don't think we know what properly is. I certainly won't claim to have all the answers. It just strikes me that all three languages have made similar changes, but handled the versioning differently. Yet none has made it easy to talk about outside their respective communities. In particular, it's hard to talk to managers at $work, where I don't control my own computing environment. It's awkward having to explain why Python 2.7 is newer than Python 3 or why it's so important to get Ruby 1.9.3 when we already have Ruby 1.9.2.