Mailing-List: contact embperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Mime-Version: 1.0
Message-Id: <p05300919ba06d9818ac0@[192.168.1.104]>
In-Reply-To: <20021124103339.18583f00.luiz@engenhosolucoes.com.br>
References: <200211230008.09049.sutra@rogers.com>
 <20021124103339.18583f00.luiz@engenhosolucoes.com.br>
Date: Sun, 24 Nov 2002 14:34:56 -0500
To: "Luiz Fernando B. Ribeiro" <luiz@engenhosolucoes.com.br>
From: Kee Hinckley <nazgul@somewhere.com>
Subject: Re: Embperl::Object and ErrorDocument
Cc: embperl@perl.apache.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

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 works fine with Embperl 1.3.4.

My EmbperlObject templates check the Execute result (and \@errors) 
and if there is an error, they clear it and then executes an error 
page.

However that doesn't address the problem of an error in an Execute 
several levels down the call chain.  It also runs into problems if 
you've done any output before displaying the error page (that's why I 
requested recently that the Perl interface be given access to the 
ability to clear the current output buffer).
-- 

Kee Hinckley - Somewhere.Com, LLC
http://consulting.somewhere.com/

I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.

---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org