hi,
I have a litle suggestion to Apache::Registry -
I tried to change it to allow script writers
to see compile errors in a browser.
I'am using mod_perl at my work ( its great - you know )
but there are few other people working on the same server with me.
All our error messages went to one
Jacek Ostrowski ([EMAIL PROTECTED]) said something to this effect:
> hi,
>
> I have a litle suggestion to Apache::Registry -
> I tried to change it to allow script writers
> to see compile errors in a browser.
>
> I'am using mod_perl at my work ( its great - you know )
> but there are few ot
On Sun, 19 Nov 2000, Jacek Ostrowski wrote:
> hi,
>
> I have a litle suggestion to Apache::Registry -
> I tried to change it to allow script writers
> to see compile errors in a browser.
>
> I'am using mod_perl at my work ( its great - you know )
> but there are few other people working on
On Thu, Jan 11, 2001 at 10:18:30PM -0800, [EMAIL PROTECTED] wrote:
> thanks for your contribution, however, Apache::Registry is not accepting
> any new features. have a look at Apache::{PerlRun,RegistryNG,RegistryBB}
> new features should fit in here or be in its own subclass. i don't think
> th
darren chamberlain wrote:
>
> Jacek Ostrowski ([EMAIL PROTECTED]) said something to this effect:
> > hi,
> >
> > I have a litle suggestion to Apache::Registry -
> > I tried to change it to allow script writers
> > to see compile errors in a browser.
> >
cut
>
> Why not just use CGI::Carp? The fa
Jacek,
While CGI::Carp admittedly doesn't catch everything, it does catch quite a
few problems.
The problem lies in the fact that Apache::Registry loads the script in
memory and attempts to compile it using eval.
When you compile a perl block with eval and there is a syntax error in that
Per
