Can you help by explaining what this does that is different from CGI::Carp?
What are you doing that is Apache specific? Could CGI::Carp do the job? If
there was something you needed added to CGI::Carp, would it make sense for
you to add the apache-specific function flag to CGI::Carp instead of making
a brand-new module?
At 12:37 AM 11/30/00 -0500, T.J. Mather wrote:
>I've done a lot of programming under mod_perl and I got tired of
>examining the error logs for errors. So I wrote a module that displays
>to the broswer the error (with a complete call stack) for any fatals or
>warnings that occur on a development server (similar to using CGI::Carp
>qw(fatalsToBrowser);), or emails the site administrator for errors on a
>production server.
>
>This has been released on CPAN as Apache::PageKit::Error, but since it
>doesn't depend on Apache::PageKit at all, I'm thinking of releasing it as
>a seperate module. Do you think this is worth doing? What should it be
>called? Is Apache::Carp a good name?
>
>Documentation can be found here (with the old Apache::PageKit::Error name)
>http://search.cpan.org/doc/TJMATHER/Apache-PageKit-0.05/lib/Apache/PageKit/Error.pm
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
__________________________________________________
Gunther Birznieks ([EMAIL PROTECTED])
eXtropia - The Web Technology Company
http://www.extropia.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
