Re: Strange interaction between command line and encoding

Update: OK, I think I am way off base... The original usage has a "fat-comma" on the right side of STDOUT which makes it a string anyway... I can't even claim no coffee since I don't drink it! Ah well...

OK, I may be way off base, but using B::Deparse to see how perl treats the -M command line switch shows it's processed as:
use encoding (split(/,/, 'utf16,STDOUT,utf8', 0));
[download]
That seems to indicate that the problem is that STDOUT is just a string rather than the actual filehandle when it's passed into encoding::import via the -M command line parameter.

HTH

-- Brian

Comment on Re: Strange interaction between command line and encoding Select or Download Code

Replies are listed 'Best First'.
Re^2: Strange interaction between command line and encoding by VSarkiss (Monsignor) on Jun 02, 2006 at 20:48 UTC
Actually, perlrun says the same thing under the handling of the `-M` parameter. But in fact, it is just the string `STDOUT` being passed to the pragma, even in the program. To pass the filehandle (in a simple way, without using lexicals or other modules), you would usually pass a reference to the glob, as in: `# WRONG use of encoding pragma, just an example use encoding 'utf16', \STDOUT, 'utf8';` [download] But anyway, as to the true source of the problem, I gave up trying to figure it out, as noted in the update. Do not rebuke them with harsh words ... but rather lead them gently - with URLs - so that they may learn wisdom.*	[reply] [d/l] [select]
Re^2: Strange interaction between command line and encoding by ikegami (Patriarch) on Jun 02, 2006 at 20:34 UTC
But `STDOUT => "utf8"` return strings too! It's equivalent to `'STDOUT', "utf8"`.	[reply] [d/l] [select]