Thanks for the spot Fred.
The issue was is that we had almost all accessors settable, as I worked
through those I've made of them read-only, which wasn't always right. Please try the current cvs or the patch below [1].
Current cvs did the trick, thanks.
:)
Now if you could go through the mp2 accessors and check if I've missed
some other (and which should be read/write), that would be a lot of help. It's probably the easiest if you use the pod manpages from here: http://perl.apache.org/download/docs.html
The mp1 methods are documented here: modperl-docs/src/docs/1.0/api/Apache.pod
The corresponding mp2 methods will be here: modperl-docs/src/docs/2.0/api/Apache/*
Sure I can do that no problem. Will probably add tests to the TestAPI packages to determine if any other read/write accessors missing unless there is a more efficient way that I'm not seeing here.
No, Fred, we don't want just any accessors to be settable, only those that make sense and those that were settable in mp1, if things haven't changed in Apache2.
More tests is always good, but if looking at the manpages: modperl-docs/src/docs/2.0/api/Apache/* is not good, for a few structures accessors you can check:
modperl-2.0/xs/maps/apache_structures
accessors starting with < are read-only.
for the complete mapping legend see %ModPerl::MapUtil::disabled_map in modperl-2.0/lib/ModPerl/MapUtil.pm
Thanks.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
