Re: Should php3_fopen_for_parser change the current working directory?

> In response to my question, Rasmus correctly noted: > >It would break a whole lot of scripts out there that expect to be in the > >same dir as the script being executed. > > Looking at the current SAPI extensions, it would seem to me that this > applies to current versions of Apache and CGI. As both AOLServer and ISAPI > are multi-threaded, it would seem to me that PHP scripts can make very > little assumptions with respect to the current working directory. It > apparently is also an issue for Roxen. It completely blows my servlet > implementation out of the water (once I have done some testing on Linux and > resolve this issue, I'm ready to check my code in). > > I believe that Sascha and David are on the right long term path. For the > short term, I would like to propose that this code be guarded with an IFDEF > specifically for Apache and CGI. > > Any objections? Sounds ok to me. My objection was to removing it completely. We definitely need to get rid of it when we are running in threaded mode. -Rasmus