Thanks much for your various suggestions.
> recommend removing the ampersand from the function call: it is bad practice
> in anything but very old Perl.
Thanks. That deprecation hasn't made it into "man perlsub" yet, except for when
one is using prototyping.
> I would also prefer to lose a few parentheses, purely for the sake of
> readability. So please try this:
>
> @res = split(/\n\n/, $in{res} = NmlML($in{res}), -1);
I have tried it, and it behaves identically to the original version.
> Could you
> just for fun add a few empty lines (say 50 or so) just before the line 1297
> and see if you then get the same error on line 1347?
I have tried adding a couple of different large numbers of blank lines, and
this made no difference. Note that when I inserted a nonblank but irrelevant
statement, such as "warn 'hello';" or "my $nothing = 'nothing';", the problem
disappeared.
> Every CGI program should be testable from the command line. But if that
> doesn't work, there is a way to remotely invoke the debugger in this
> situation. http://
> www.foo.be/docs/tpj/issues/vol4_3/tpj0403-0008.html .
Thanks. The applicability of this approach is unclear to me. The document says
"The ptkdb window will appear". But this script is being run by httpd to
generate a reply to a request from a web browser's form submission. I don't
understand where a window could appear.
As for the command line, yes, but I would be simulating a multipart/form-data
http form submission with a file-upload part and hoping that Perl is seeing the
same thing. This seems dubious to me. I have uploaded hundreds of files without
getting this bug, and even this file works fine if I add a few characters to,
or subtract a few from, it.
ˉ
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
