binmode in 1-liner?

[Larry]

I am a big fan of Perl 1-liners and I even use them on Windows. One
thing that bugs me though is that there doesn't seem to be an easy way
to process binary files with 1 liners. It would be nice if there were
a command-line switch to turn on "binmode". As it is, I am forced to
use

perl -0777 -ne "BEGIN { binmode STDIN; binmode STDOUT } ... "

which is a lot of typing for a 1-liner.

 

[Dr.Ruud]

Larry:

I am a big fan of Perl 1-liners and I even use them on Windows. One
thing that bugs me though is that there doesn't seem to be an easy way
to process binary files with 1 liners. It would be nice if there were
a command-line switch to turn on "binmode". As it is, I am forced to
use

perl -0777 -ne "BEGIN { binmode STDIN; binmode STDOUT } ... "

which is a lot of typing for a 1-liner.

Use a wrapper.

Maybe call it 'perlb.pl' (assumes you have added 'pl' to the executable
extensions).

 

[Mark Clements]

I am a big fan of Perl 1-liners and I even use them on Windows. One
thing that bugs me though is that there doesn't seem to be an easy way
to process binary files with 1 liners. It would be nice if there were
a command-line switch to turn on "binmode". As it is, I am forced to
use

perl -0777 -ne "BEGIN { binmode STDIN; binmode STDOUT } ... "

which is a lot of typing for a 1-liner.

You can set the environment variable PERLIO to accomplish this. see

perldoc perlrun

for details.

Not quite the same, of course.

The other alternative would be to create a module that does the
necessary in its BEGIN block. You could then

perl -MMyBinModeModule -le "...........

though probably choosing a shorter name for the module.

Mark

 

[Anno Siegel]

You can set the environment variable PERLIO to accomplish this. see

perldoc perlrun

for details.

Not quite the same, of course.

The other alternative would be to create a module that does the
necessary in its BEGIN block. You could then

If it's a module, the BEGIN {} doesn't make a difference. If it's
loaded via "use", it will be run at compile time (relative to the
calling script) anyway. If it's via "require", BEGIN {} in the module
doesn't help any.

Anno

 

[Mark Clements]

If it's a module, the BEGIN {} doesn't make a difference. If it's
loaded via "use", it will be run at compile time (relative to the
calling script) anyway. If it's via "require", BEGIN {} in the module
doesn't help any.

OK: I should have thought of this. Thanks for the correction.

Mark