On Fri, Apr 15, 2005 at 07:25:31PM +0100, Joseph Walton wrote: [snip]
> Sorry for a the lengthy response - none of those solutions is more > than about five lines, and it's really a question of policy rather than > mechanism. The submitter suggests something like this: Change the documentation to better explain what ENCODING does, and why it won't work with scalar refs for OUTPUT. Also document that the strings will be stored as Perl's unicode. Then add the check for passing both and die. Actually, considering PerlIO now gives :encoding for files, you might want to mark ENCODING deprecated, too. From my perspective, it would be enough to die with a sensible error if both options are passed in, since they don't work together. KEN -- Kenneth J. Pronovici <[EMAIL PROTECTED]>
pgpE2pBelO3mB.pgp
Description: PGP signature
