On Sun, Nov 24, 2002 at 11:01:15PM -0500, David Williams wrote:
> I admit that my legacy embperl code really sucks. Unfortunately there's
> thousands of lines of it and I have angry customers who are waiting for the
> upgrade to be complete, so I am asking for something more than criticism of
> old
I admit that my legacy embperl code really sucks. Unfortunately there's
thousands of lines of it and I have angry customers who are waiting for the
upgrade to be complete, so I am asking for something more than criticism of
old code... Is there a way for my old crappy code to work under Embperl2c
a
At 8:12 PM -0500 11/24/02, David Williams wrote:
http://www.conceptionstore.com>
becomes:
which is un-renderable.
However it is in fact a perfect representation of what you had.
According to the HTML spec, your href value ended at the colon after
http. Even if Embperl didn't rewrite the U
Here's what's happening:
I was using Perl 5.6.x, HTML::Embperl 1.3.4 and Apache 1.3.x for a long time
without problems. However I have just upgraded my server to RedHat 8.0 which
has Perl 5.8.0, Apache 2.0.x and then I followed Gerald's instructions for
grabbing and compiling the latest Embperl2c
At 10:33 AM -0200 11/24/02, Luiz Fernando B. Ribeiro wrote:
I use a [$ sub error $] in my base.epl that do do all the error handling
and in the end it exits with a normal exit;
In my other pages after any eval {}; or other error I call that sub with
$req->error('tittle', 'page', $error);
It work
Em Sat, 23 Nov 2002 00:08:09 -0500
Jordan Baker <[EMAIL PROTECTED]> escreveu:
> Aha, well I discovered something by testing tonite.
>
> I do a couple Execute calls in my base.epl and essentially they hide
> the error from the parent process.
>
> So I have to find a way to propogate errors.. perh
