Stas Bekman wrote:
Also, these two: $Apache::Server::SaveConfig, $Apache::Server::StrictPerlSections need to move to the package they belong to. Which is Apache::PerlSections::. And you can now call it:
Apache::PerlSections::Strict. But that's a separate issue.
I'll change those names sepraratly in just a moment, it does make much more sense.
cool. As Apache::Server is really no more at the moment. (moved to ServerRec)
But in regards to the strict perl sections issue, what are we doing about it?
$Apache::Server::StrictPerlSections * Get rid of it ? * Keep it only when MP_COMPAT_1X=1 * Warn about it being deprecated in favor of eval {}
$Apache::PerlSections::Strict on by default, and optionnaly disableable ?
Suggestion:
Get rid of it completely, not even with compat or MP_COMPAT_1X. Those who will want to try to reuse 1.x and 2.x config file, can add eval {} in their 1.x setup and remove $Apache::Server::StrictPerlSections in mp1. document that in porting/compat.pod.
So, this would also mean no $Apache::PerlSections::Strict either ?
-- -------------------------------------------------------------------------------- Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5 http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5
signature.asc
Description: OpenPGP digital signature
