note davido <p>There are just a few things to grasp at first, and then it becomes easy. </p> <p>First, you probably already know this, but with the -e option on the command line, you can follow it with a string of Perl code to be executed. Some operating systems prefer the code to be enclosed in single quotes, and some in double. An example could be:</p> <code> perl -e "print qq/Hello world!\n/;" </code> <p>Notice I used the qq// quotes instead of "" (double quotes). This was done because the entire string of code is wrapped in double-quotes, and it would confuse the command shell if you start embedding other similar quotes within the one liner. Some OS's allow for escaping, but it's easier just to avoid that issue altogether by using alternate quotes. </p> <p>The next thing to understand is the -n option. -n opens each file listed on the command line, and iterates over each line in the file. On each iteration, $_ is set to that line of data. Here's an example: </p> <code> perl -n -e "print qq/$.:\t$_\n/;" textfile.txt </code> <p>The preceeding will iterate over each line in 'textfile.txt', and print that line, along with the line number of the file (that's what the $. special variable contains).</p> <p>Consider the -n option to be roughly equivilant to: <code>while( <> ) { ........ }</code>, where you get to specify what goes inside of the <code>{ ......... }</code> block. </p> <p>Since a lot of one liners need to output the file they're iterating over, we can save typing by using the -p switch, instead of -n. -p does the same as -n, but has an implicit <code>print $_</code> on each iteration of the loop. Think of -p as this: </p> <code> while ( <> ) { .......... # Your code goes here. print $_; } </code> <p>This is often put to use by specifying some action that acts upon $_ in some way. If you modify $_ on each iteration, its modified content will be output for each line. Here's an example: </p> <code> perl -pe "s/\bperl\b/Perl/g;" textfile.txt </code> <p>This will iterate over "textfile.txt", and substitute all occurrences of 'perl' with 'Perl'. The result is dumped to STDOUT, unless you redirect it. ...let's redirect it to a tempfile: </p> <code> perl -pe "s/\bperl\b/Perl/g;" textfile.txt >temptext.txt </code> <p>Easy huh? Ok, now it gets better. Many times you just want to do what's known as an in-place edit of your input file. The -i option does that. With the -i option, you can specify just -i, and leave it at that, or you can specify -i.bak to tell Perl to output a backup file before acting upon the original file. '.bak' was chosen arbitrarily. It could also be -i.hello -i.old, or whatever other extension you want to give the backup file. Here's how you put inplace editing to work: </p> <code> perl -pi.bak -e "s/\bperl\b/Perl/g" infile.txt </code> <p>This will iterate over each line of infile.txt, changing each occurrence of 'perl' to 'Perl', and then saving that change. A backup of the original file will be saved as infile.txt.bak </p> <p>Another commandline option is the -M option. -M is the same as "use ...." So if you say, <code>perl -MData::Dumper -e "print Dumper \%::"</code>, it's the same as including the line "use Data::Dumper" at the top of your script. </p> <p>There you go.... all the ammo you need for basic one-liners. You can get a lot more complex with it than that, and I have only hit on a few of the command-line options. See [doc://perlrun] for a list of all commandline options, as well as a description of how to use most of them. </p> <p>Have fun!</p> <p>Your question also mentioned <code>pack</code>. This function, and its counterpart 'unpack' are discussed in Perl's [doc://perlfunc] under [doc://pack] and [doc://unpack]. Perl also comes with a great pack/unpack tutorial called [doc://perlpacktut]. The tutorial ought to really give you more than you ever wanted to know about pack and unpack.... HTH.</p> <p><small><b>Update:</b> Fixed missing -e per [Aristotle]'s sharp eyes.</small></p> <div class="pmsig"><div class="pmsig-281137"> <br /><p>Dave</p> </div></div> 421195 421195