Hello,
>
> I'm having trouble with the common technique (alarm eval{}) to avoid
> blocking operations. The die message is always going to the browser
> even when trapped by the eval block.
>
I don't have an idea at the moment what's going wrong here. Embperl itself
doesn't sets $SIG{__DIE__
> i was trying to do '!Fields' => 'function(foo, bar) AS baz', which
> confused DBIx::Recordset->BuildFields, since it does (basically) a
> split on /,/.
>
> So i patched it to take !Fields as an array ref, in which case it assumes
> you have already separated the fields appropriately.
>
That's a
>
> Now I wish to import it to embperl mode.
> I used $http_headers_out{Content-type} = "application/octet-stream";
> $http_headers_out{Content-Disposition} = "attachment; filename=demo.tmp";
>
Because the header names contains a minus you need to quote them, otherwise
Perl will treat it a a expr
On Tue, Feb 19, 2002 at 04:48:13PM -0300, Luiz Fernando B. Ribeiro wrote:
> I'm having trouble with the common technique (alarm eval{}) to avoid
> blocking operations. The die message is always going to the browser
> even when trapped by the eval block.
>
> eval {
try adding:
local
Hello,
I'm having trouble with the common technique (alarm eval{}) to avoid
blocking operations. The die message is always going to the browser
even when trapped by the eval block.
eval {
local $SIG{ALRM} = sub {die};
alarm 3;
open(FIFO,">$fifo");
alarm 0;
};
if ($@) {
Hi!
I have used
print "Content-type: application/octet-stream\n";
print "Content-Disposition: attachment; filename=demo.tmp\n";
print "Content-Description: sample\n\n";
to dump some files from mySQL databases.
Now I wish to import it to embperl mode.
I used $http_headers_out{Content-type} = "ap
