----- Original Message ---- From: Smylers <[EMAIL PROTECTED]> > I've been caught out by passing something like a Path::Class::File > object, which stringifies just fine as a file path, to modules like this > if only they'd just treat it as a string -- but instead overjealous > checking spots that it's a reference and declines to stringify it.
If someone tries to parse a Path::Class::File object as TAP, I will cackle with glee as I choke them to death if they dare to file a bug report. However, a note will be made in the docs. If you can come up with a use case for this scenario, let me know and I'll consider it. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
