Stas Bekman wrote:
Philippe M. Chiasson wrote: [...]
Moreover now that I think about it I'm not quite sure why in the world someone will want to turn this feature on. Can you please remind me why was it added at all? If someone wants that badly then can just wrap the whole section in the eval {} block.
As far as I can tell/remember, this is simply a mp1 feature that I wanted to
preserve when porting the <Perl> code to mp2.
I agree that it doesn't add much functionnality that an eval {} block wouldn't
allow (except maybe if the code _doesn't_ compile at all.
How about this?
- Implement PerlSectionsNonFatal = 1
- Deprecate StrictPerlSections with a warning, unless MP_COMPAT_1X is selected ?
If we agree that it has no real added value then we don't want it at all.
Unless somebody can come up with a good reason why we need it, I am quite happy getting rid of this 'feature'
Though if we want to have it for backward compat, then we better keep the same name.
So, +1 to keep the name and do have it only for MP_COMPAT_1X
Will do that then, expect revised patch.
Next it'd be nice to remove the mentioning of it in
src/docs/2.0/api.orig/Apache/PerlSections.pod and move it to user/porting/compat.pod. We shouldn't even mention backcompat features in the normal docs - only in the compat.pod.
Sounds good.
-- -------------------------------------------------------------------------------- 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
