Arthur Bergman wrote: >>>For mod_perl I think the biggest improvment over 5.6.1 is the fact that >>>a) why use _r functions >>> >>Can you please expand on this one? Do you mean that in 5.6.1 one has to >>use _r equivalents instead of certain unsafe POSIX functions to achieve >>thread-safeness and 5.7.x has this transparent to developers? >> > > I meant, we use _r functions > > for example CORE::localtime() now uses localtime_r instead of localtime() so it is >safe to call it from multiple threads
cool! That means that we better require perl 5.7.x for threaded mod_perl, or need to provide some wrappers via CORE::GLOBAL to override unsafe functions in 5.6.1 Is it possible to backport these to 5.6.2? >>>b) regexes are threadsafe >>> >>what about things like chdir? >> >> >> > > chdir() cannot be threadsafe ;), there is only one CWD per application. (sadly) :( Are there any plans for providing alternative/extended open(), require() and other calls that may rely on the relative to the current dir paths (when the code does use 'chdir' and we override it with something else)? or should each project develop their own workaround? We are talking about providing solutions to people porting their code to mod_perl 2.0 and those who run plain scripts under Registry, so they won't need to rewrite/redesign the code, at least to get them running during the transition period. _____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
