IO::All does this.

Great module! So with IO::All this could yield:

$ perl -MIO::All -F'/\t/' -lnae '@files = @F, next if 1 .. 1; @f = @fi
+les; $_ >> io(shift @f) for @F' <<EOF
id    name    position
1    Nick    boss
2    George    CEO
3    Christina    CTO
EOF
$ paste id name position
1    Nick    boss
2    George    CEO
3    Christina    CTO
[download]

EDIT Removed do statement.

Greetings,
-jo

$gryYup$d0ylprbpriprrYpkJl2xyl~rzg??P~5lp2hyl0p$

I don't think it's a good idea to overload two very different operators like > "greater-than" and >> "shift".

That's begging for inconsistency problems. (like syntax, precedence, name it ...)

So my tangential question: Is there a way to "export" the no warnings 'void' from inside the streaming package, rather than requiring it in ::main? It would be best if it could just turn off the warnings for the streaming objects, but leave the warnings on for non-overloaded uses of comparison and bitshift. I tried putting the no-warnings inside the overloaded functions, to try to keep the scope limited, but that's not the right place to prevent the warning. (Yes, I understand this isn't necessarily good practice, or "nice" to the external user. This is just for my own curiosity, and not something I'd put in practical code.)

That's another good example why overloading is doomed to fail if the operator isn't semantically compatible.

Regarding your question:

Either you can try to manipulate the __WARN__ handler in %SIG

Or you can try exporting warnings inside import() like demonstrated in Modern::Perl

(And I agree about the productive code part. ;)

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}

Updates

Rephrased and linked

I'm not much of a fan of operator overloading anyway. But I thought it was a nice thought experiment, and again, maybe acceptable for oneliners.

I still tried to cheat the system and go around the "useless use [...] in voix context" by using <<= instead of << because $magic << "Value"; returns $magic itself so $magic <<= "Value"; works fine.
Except it failed when trying to turn this: $magic << "Value" << "Other value"; into $magic <<= "Value" <<= "Other value";, because << is a left associative operator and <<= is a right associative one. Meanig you've just turned ($magic << "Value") << "Other"; into $magic <<= ("Value" <<= "Other");. Whoops.

So yes, the lesson is don't add new semantic to operators kid (yup, I'm looking at you C++).