You can avoid the "newline" problem (and have a much more useful script) if you learn to use @ARGV (array of command-line parameters). Another useful trick for this script is to read the file in "slurp mode":
#!/usr/bin/perl
use strict;
if ( @ARGV != 2 ) {
die "Usage: $0 pattern file.name\n";
}
my ( $find, $filename ) = @ARGV;
open( my $fh, "<", $filename ) or die "Cannot open $filename: $!\n";
$/ = undef; # set INPUT_RECORD_SEPARATOR to "slurp-mode"
my $seq = <$fh>; # entire file is now in $seq;
$seq =~ tr/\n//d; # remove all newlines (I think you don't want space
+s)
open( my $out, ">", "write.txt" ) or die "Cannot create write.txt: $!\
+n";
while ( $seq =~ /(..)$find(..)/g ) {
print "before = $1 ; after = $2\n";
print $out "$1\n$2\n";
}
You then provide the "find" pattern and the input file name after the name of the script when you run it:
your_script_name agt input_file.name
# or:
perl your_script_name agt input_file.name
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.