in reply to Re^7: unpacking wmic command's unicode output
in thread unpacking wmic command's unicode output

how would it hurt?

>perl -e"print qq{C\x00a\x00p\x00}" | perl -CS -we"print length <>"
6

[download]

Why does it seem not to hurt in my use now?

Because -CS has no effect if there are no bytes with bit 7 set.

Replies are listed 'Best First'.
Re^9: unpacking wmic command's unicode output
by goibhniu (Hermit) on Nov 12, 2008 at 21:19 UTC

    but that's not -CS's fault, as it prints 6 without -CS as well. Or am I missing something still?

    #my sig used to say 'I humbly seek wisdom. '. Now it says:
    use strict;
    use warnings;
    I humbly seek wisdom.
[reply]

      Ok, I'll cede that while it has an effect (data from STDIN should be considered decoded), saying it's harmful is incorrect.

      However, it doesn't fix the problem it's suppose to fix. As a solution, it's useless and therefore wrong.

[reply]
        As a solution, it's useless and therefore wrong.

        Hm. That's a bit strong. As a solution, it produces the desired result. Ie. The data in the file is sans unicoding.

        The fact that the -CS isn't actually responsible for that--nor even perl itself directly--doesn't detract from the usability of the solution to produce desired result.

        As it turns out, wmic process | perl -pe1 > file also produces the desired result, and as its 3 characters shorter I guess that makes it a superiour solution. I would have suggested that; had I thought to have tried it.

        It turns out that it just going via a pipe that causes wmic.exe to produce ansi output rather than unicode, so a simple wmic process | tee > file works.

        And it's even shorter.

        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom