Geoffrey Young wrote: [...]
It had to be fixed locally in mp2 since 5.8.1 has been released already, meaning that anybody who uses 5.8.1 is vulnerable to this problem. Hopefully 5.8.2 will get it fixed in perl.
well, I guess that was kinda my question. as an application itself, perl will always have bugs, so I guess I was asking if it was mod_perl's responsibility to "fix" these bugs internally.
but if you can't calculate memory usage accurately, that's probably a good enough reason so take care of it.
Well, that was just an example that caused a problem to my program, I would have fixed it anyway, since you never know how important things are to other people, who may have uses that we don't know about. So if you find something that doesn't work as advertised specifically under mod_perl it should be fixed in mod_perl if at all possible, no matter if it looks important or not.
Here is another possible example: let's say you want to kill (or send some signal to ) the parent process. One of the recipes is to do 'kill getppid(), $signal' which will try to kill the init process (oy wei!).
__________________________________________________________________ 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]
