Thank you tachyon. In writing the dummy script, I left all the "use" statements in place for various modules that the (quite old) original script used. (and of course, for brevity I left them out of my post here - d'oh!)

amongst them was a "common" module that parsed form data into a Hash %common::field.

So, when CGI is used after, STDIN is empty because it has already been read.

And I spent 2 F&*^%ing hours looking for a complicated solution. Ah well, always the way...

Thanks all for your comments. Now all I have to do is find out which scripts use the "common" module and slowly move them over to CGI...

cLive -;)

--
seek(JOB,$$LA,0);

In reply to (cLive ;-) Re: Bizarre CGI.pm behaviour or just me? by cLive ;-)
in thread Bizarre CGI.pm behaviour or just me? by cLive ;-)

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.