Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Hi there anonymonk, thanks for posting the code. A few comments for you:

  • You seem to read in the file just fine. I'm willing to bet the farm that the tab-delimited formatting is still in your $info variable. However, when you print the variable to the browser, it won't display the tabs properly. Your browser should treat all whitespace characters as just spaces, so tab alignment won't work. You can verify this by viewing the source of the output in your browser -- the HTML source should show the tab alignment. I'm sure that if you printed out <pre> tags around the data, it would appear better in the browser output.
  • You have a problem when you try to slurp the file contents into $data. More specifically, you try to use the diamond <> operator on a string ($info), which won't work. You can only use this operator on filehandles. This is why nothing was showing up. If you had warnings turned on, you would have seen an error to this effect.
Otherwise, your code looks good. Of course, I would be remiss if I didn't strongly encourage you to use strict and warnings! This is Perl Monks after all!

blokhead


In reply to Re: Re: Re: why do CGI's mess everything up??? by blokhead
in thread why do CGI's mess everything up??? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others rifling through the Monastery: (6)
As of 2024-04-25 11:20 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found