Front page | perl.perl5.porters |
Postings from May 2003
Stas Bekman wrote:
>
> However I'd very much like to have a mechanism to shut this warning up. The
> reason: if you are using Apache::Reload while developing mod_perl modules,
> inability of shutting down this warnings forces you to avoid the usage of
> constants, because you want to keep your error log free of useless (for
> development purpose) clutter. I want to be able to shut those down, and I'm
> aware of the consequences. It sounds like a not perl-ish way, if you can't
> make perl quiet.
You can always trap warnings via $SIG{__WARN__}.
The problem with Apache::Reload is that it may leave around some modules
compiled with the old constant, and compile newer ones with the new value
of the constant. (Remember that constants are inlined.) That's why I'm
not confortable with having this warning easy to disable.
(Maybe an ad-hoc optional $SIG{__WARN__} handler could go
into Apache::Reload ?)
Thread Previous
|
Thread Next