Front page | perl.perl5.porters |
Postings from May 2003
Stas Bekman <stas@stason.org> writes: >> >> http://archive.develooper.com/perl5-changes%40perl.org/msg04919.html > >Thanks for the reference reading, Rafael. > >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. The snag is that code that has been _compiled_ will be using the old version of the constant despite the newly read code defining as something else. So we could shut up the warning but we cannot turn off the problem it is warning about. -- Nick Ing-Simmons http://www.ni-s.u-net.com/Thread Previous | Thread Next