Given that we can't make it throw, but it's likely used in *lots* of baby perl type code, I increasingly think that an advisory warning is the least horrible thing we can do to our users. Does anybody have an objection and/or a better idea? -- Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a clue http://shadowcat.co.uk/blog/matt-s-trout/ http://twitter.com/shadowcat_mst/ Email me now on mst (at) shadowcat.co.uk and let's chat about how our CPAN commercial support, training and consultancy packages could help your team.Thread Previous | Thread Next