You have much more experience writing software for others than I do so I will take your advice. There were comments made by diotalevi and others in the CB that I will take as well. I solicited comments because I don't do this for a living ;-)

You could make that argument, but it fails when you need to use those builtins inside the package that defines those methods. And, just because Unix is vowel-deficient doesn't mean that you need to be. :)

--
brian d foy <brian@stonehenge.com>
Subscribe to The Perl Review

You could make that argument, but it fails when you need to use those builtins inside the package that defines those methods. And, just because Unix is vowel-deficient doesn't mean that you need to be. :)

Well - that depends on how you call them. As long as you carry on calling them as methods you'll be just fine - inside the declaring package or not.

Personally I'm anti using keywords in procedural/functional APIs for exactly the reason you put forward. For OO interfaces I think it's fine - as long as the functionality matches the keywords they're copying. pos works well for me in this instance.