Sascha, What I, at least, fail to understand is the answer to Rasmus' initial question(s): - Are we going to break compatibility? If not, then why are we spitting out this error by default?
Given what I've seen here in the last few days, I think it's fair to say that this notice will cause quite a bit of havoc. Even if the evolution of the session module ended up leaving lots of the code out there in a suboptimal state, if we have no intention to break compatibility, there's no reason to 'annoy' people into changing their working code. Even if we do plan to break compatibility, it's best if we follow the lead of allow_call_time_pass_reference, and default to having this warning off. Zeev At 21:36 11/10/2002, Sascha Schumann wrote: > > This is the exact same code run twice. It works exactly the same both > > times. Where is the silent failure? > > The second change will not have any effect. It will be lost. > The session module does not see it. The module looks at > $_SESSION first, and if it does not find anything, falls back > to the global sym table. > > You can try it yourself by firing up PHP 4.2 and running the > script from this test case. > > http://lxr.php.net/source/php4/ext/session/tests/008.phpt > > - Sascha > > >-- >PHP Development Mailing List <http://www.php.net/> >To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
