in reply to Re^3: Using pipes to combine scripts
in thread Using pipes to combine scripts

Correction: it wasn't a cool use for you. It was, however, a cool use for me, and possibly others who are not experts at Unix.

The point I was trying to make (see <em>phasis on Perl) is that however cool that may be from your, or anyone else's, POV including mine, it has nothing to do with Perl itself. There are tons of things that are cool for me, some of which are appliable also to perl scripts, but such that the perlishness of the latter ones plays no role whatsoever in their coolness.

Also, while none of us all was born learnt at anything, and I can appreciate your enthusiasm which reminds me of my own whenever I discover something new, this is hardly a thing for "unix experts". Indeed I'd rather rate it around the ABC of shell (not only *NIX ones!) interaction, i.e. a "@{[('very') x 5]}" elementary thing, which I suppose is the reason why it was unvoted so much.

Replies are listed 'Best First'.
Re^5: Using pipes to combine scripts
by bart (Canon) on Nov 19, 2006 at 22:58 UTC
    That is, IMO, a limitation of this site. The coding tip from esk555 is indeed not a "Cool Use For Perl", but OTOH there is no section here for mere "Practical Tips For Perl Programmers". So he had to put it here, by lack of a better place. (where else... Code Catacombs? Snippets?)

    The real irony, to me, is that if he had posted the exact same node as a reply to a SoPW question "How can I combine scripts on the same command line?", it probably would have gotten a lot of upvotes. There regularly are nodes of this type, in Daily Best Nodes.

    p.s. His tip is indeed worthwhile for Windows programmers, who aren't used to this kind of thing. The only tools that I know of on Windows that commonly used in this way, are ports of Unix utilities, such as UnxUtils.

[reply]

      Good points! As far as the appropriateness of an answer in such terms in SoPW, that's because occasionally people would ask about how to "combine scripts" possibly thinking of something very Perl specific, wheareas shell interation would do.

      As a side note Windows does come with its own file/text utils, descendent from old DOS ones, and probably inspired by UNIX ones (although note that IANAOH - I am not an osen historian). Of course it's apparent that the former ones are much less powerful and less prone to be combined each other than the latter ones. Anyway you can get a full list of them by just typing help at the prompt. Indeed, I do have UnxUtils and stuff from similar projects intalled. Just to make my life easier, you know...

[reply]
[d/l]
      We actually have tips section, buried under tutorial section at here. They cannot be terms as 'practical' in the sense you defined though.
      --Artist
[reply]
[d/l]
Re^5: Using pipes to combine scripts
by esk555 (Beadle) on Nov 19, 2006 at 12:17 UTC
    Not to be difficult, but merely to counterpoint: Not everyone
    on the site uses Unix, and thus would possibly not be used to
    what is second nature to people like you. Granted, the majority
    of people on the site will be Unix users, but I want
    my posts to be for everyone, not merely the advanced majority.
    I hope that doesn't sound bad, it's a mere statement
    of fact.
[reply]
      Not to be difficult, but merely to counterpoint: Not everyone on the site uses Unix, and thus would possibly not be used to what is second nature to people like you.

      Not to be difficult, but merely to counterpoint: unix (or better: unix-like osen) is much less a second nature for me than you may think. However as hinted in the other post, although it all started with unix, it is a feature now available in most common shells. Actually I started using pipes and shell redirections in my (now) old DOS days when I barely knew about unix and Linux did not exist yet. Admittdly, *nix shells generally offer more powerful opportuinities in this sense, but that's a whole another story.

[reply]

In Section Cool Uses for Perl