1. use strict or die (updated)
  2. declare your variables with my
  3. Try CGI's builtin functions for generating the header, form, tags and actually all html.  use CGI qw/:html3/
  4. I wouldn't use eval to trap errors. There is an option for CGI like use CGI::Carp 'fatalsToBrowser'; (updated).
  5. The while loop could be done more concise:
    while( <GUESTS> ){ #no chomp, we need the \n later on... split /::/; if( $_[0] =~ /$search_name) { print join "<BR>\n", @_; print "<HR>\n"; } }
  6. Try use diagnostics;, maybe you like it. I do.
Jeroen
</code> "We are not alone"(FZ)

In reply to Re: C any bugs? by jeroenes
in thread C any bugs? by deriwana

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



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.