Hi jdporter,
Thanks for your thoughts, I think you're right, and if I was writing this module from scratch I probably wouldn't implement the check in the first place, or make it simpler... especially now that I see how much time went into researching it ;-) My module originally had a warning in place for all references and undefined values, the idea was to be user-friendly and prevent the user from passing references by accident, and this effort was an attempt to exclude objects that stringify from that warning. I think that I've found a solution for now (I've posted it below), which is definitely on the complex side, but I'm okay with it for now. Your idea of a tied variable returning different values is something it might not handle... I will have to test that out!
Thanks and Regards,
-- Hauke D
In reply to Re^2: Can I ask Perl if an object will stringify?
by haukex
in thread Can I ask Perl if an object will stringify?
by haukex
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |