STDOUT);'? That should
close the filehandle and flush the output. Whether that results in the
output getting pushed on through to the web client and the connection being
closed or not may depend on the server software you are using.
---Larry
+----
}
>}
>
>Is this correct ??
>Thanks and Cheers always!!
>Murli
++
| Larry Coffin, G.P.H. Watertown, MA |
| http://www.PointInfinity.com/lcoffin/[EMAIL PROTECTED] |
+
you need them:
print <So, it looks like I'm back to where I was before: splitting the string on &
>before I process %26.
>
>That's still OK. It's a better solution than what I'm doing now.
>
>Thanks again all (esp. Larry).
>
>-John
>
>On 12/10/02
>Print >> End_form;
>
>Name: $q->param("name")
>
>End_form
That's because you can't execute perl code within this construct.
It is essentially a double quoted string that just happens to span multiple
lines. So, this doesn't work just like:
print "Name $q->param('name')\n";
won't
>$q->use_named_parameters(1);
Looks like that was removed in CGI.pm version 2.57.
---Larry
+----+
| Larry Coffin, G.P.H. Watertown, MA |
| http://www.PointInfini
t;
>...unless I just use CGI.pm for variable processing. Hmmm. Would this work?
>
>use CGI;
>my $q = new CGI();
>
>print OUTPUTFILE >> End_of_form
>
>My Company Name
>Applicant's Name: $q->param("Name")
>
>E
ant just '[\d\.]'.
---Larry
+--------+
| Larry Coffin, G.P.H. Watertown, MA |
| http://www.PointInfinity.com/lcoffin/[EMAIL PROTECTED] |
+--
>In terms of "why reinvent the wheel", I prefer not to use CGI.pm for simple
>form processing because it prevents me from doing something like
>
>print >> End_of_form
>
>...lots of HTML code...
>
>End_of_form
It does? Then I must be programming in something other than Perl
because I use th
