Doug MacEachern wrote: > On Thu, 11 Apr 2002, Stas Bekman wrote: > > >>I was thinking that since our test suite loads Apache::compat other >>tests testing the real non-compat API could be affected. Shouldn't we >>move all compat tests to run under vh with its own interpreter? > > can't do that unless perl is ithreads enabled.
doh! of course. But what I think is more along the developers lines. I want to be able to run the test suite skipping all those tests that load the compat layer, to see that everything works for sure. That's why I was thinking about compat/ Though some tests using compat just because the new API is not there yet. So I guess we shouldn't move these into compat/, I think I'll try the following trick: replace Apache::compat with an empty package, and see whether things work the same way, discarding failures in modules needing the compat layer. >>Also shouldn't we start making CGI.pm play nice with modperl 2.0 without >>compat layer? > > whatever you do, don't add anymore modperl specific code to CGI.pm > it should be possible to remove most if not all the existing modperl > specific code. Actually I wasn't planning on taking any news things to work on, before I finish my ever growing todo list. I thought that somebody else will be interested in working on this issue. All I wanted to say is that I think that's it's important that CGI.pm will work with modperl 2.0 when it gets released, or even better earlier. Any takers? __________________________________________________________________ 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
