This is your actual program: open( FH, "+>toc1.ncx" );
$OH1 = select(FH);
open( FILE, 'b.txt' ) or die "$!";
while (<FILE>) {
if (
m/^(ISBN Number|book title|Cover|Half|Title|Copyright|Content|Preface)
+:(.*)/
)
{
push( @arr, $2 );
}
}
Your print statement will never execute as it was turned into a comment. So what is your question? Assume we know nothing about ".ncx"-files. Some very preliminary comments are: - You are not using "use strict; use warnings;
- You are using two argument open rather than the three argument version.
- You are not using lexical filehandles.
- "Kidnapping" the standard out filehandle and pointing it to a file is probably a bad idea. It is better to use an explicit filehandle in your print-statements.
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
