Re: [PHP-DEV] __FILE__ constant
At 06:58 PM 5/4/2001 -0400, Jon Parise wrote: On Fri, May 04, 2001 at 06:31:37PM -0400, Jon Parise wrote: ?php echo __FILE__; ? works fine here. Or do you meant something else, Chuck? The value is set; it's just missing all path delimiters. So if the file is actually /var/www/foo/bar.php, echo __FILE__ gives me varwwwfooobar.php. Which means that dirname(__FILE__) returns incorrect results. It's working fine here, too. Woops, scratch that. I see the problem now, too. It was introduced sometime between May 2nd (my last build) and today. Because now files in the Zend repository have changed in that window, I think it's probably a PHP bug. Sterling made a patch which changes the way PHP_SELF is set. Is there any chance this has anything to do with it? (It doesn't sound like it though). Can you check the history of php4/main/main.c? Andi -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] __FILE__ constant
By the way, can you open a bug report about this? Please include PHP version, Web server setup and short reproducing script. At the same time if one of you guys can get an idea what broke this (or on what day) that would be great. You can do a binary search by checking out the PHP CVS by date. Andi At 06:58 PM 5/4/2001 -0400, Jon Parise wrote: On Fri, May 04, 2001 at 06:31:37PM -0400, Jon Parise wrote: ?php echo __FILE__; ? works fine here. Or do you meant something else, Chuck? The value is set; it's just missing all path delimiters. So if the file is actually /var/www/foo/bar.php, echo __FILE__ gives me varwwwfooobar.php. Which means that dirname(__FILE__) returns incorrect results. It's working fine here, too. Woops, scratch that. I see the problem now, too. It was introduced sometime between May 2nd (my last build) and today. Because now files in the Zend repository have changed in that window, I think it's probably a PHP bug. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] __FILE__ constant
I'm unable to reproduce it with the current CVS, btw. Zeev At 17:32 5/5/2001, Andi Gutmans wrote: By the way, can you open a bug report about this? Please include PHP version, Web server setup and short reproducing script. At the same time if one of you guys can get an idea what broke this (or on what day) that would be great. You can do a binary search by checking out the PHP CVS by date. Andi At 06:58 PM 5/4/2001 -0400, Jon Parise wrote: On Fri, May 04, 2001 at 06:31:37PM -0400, Jon Parise wrote: ?php echo __FILE__; ? works fine here. Or do you meant something else, Chuck? The value is set; it's just missing all path delimiters. So if the file is actually /var/www/foo/bar.php, echo __FILE__ gives me varwwwfooobar.php. Which means that dirname(__FILE__) returns incorrect results. It's working fine here, too. Woops, scratch that. I see the problem now, too. It was introduced sometime between May 2nd (my last build) and today. Because now files in the Zend repository have changed in that window, I think it's probably a PHP bug. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- Zeev Suraski [EMAIL PROTECTED] CTO co-founder, Zend Technologies Ltd. http://www.zend.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] __FILE__ constant
http://www.php.net/bugs.php?edit=1id=10644 And it happens to me too.. --Jani On Sat, 5 May 2001, Andi Gutmans wrote: By the way, can you open a bug report about this? Please include PHP version, Web server setup and short reproducing script. At the same time if one of you guys can get an idea what broke this (or on what day) that would be great. You can do a binary search by checking out the PHP CVS by date. Andi At 06:58 PM 5/4/2001 -0400, Jon Parise wrote: On Fri, May 04, 2001 at 06:31:37PM -0400, Jon Parise wrote: ?php echo __FILE__; ? works fine here. Or do you meant something else, Chuck? The value is set; it's just missing all path delimiters. So if the file is actually /var/www/foo/bar.php, echo __FILE__ gives me varwwwfooobar.php. Which means that dirname(__FILE__) returns incorrect results. It's working fine here, too. Woops, scratch that. I see the problem now, too. It was introduced sometime between May 2nd (my last build) and today. Because now files in the Zend repository have changed in that window, I think it's probably a PHP bug. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] __FILE__ constant
Can you please try and check on what date (and maybe what patch) broke this? Thanks, Andi At 05:11 PM 5/5/2001 +0200, Jani Taskinen wrote: http://www.php.net/bugs.php?edit=1id=10644 And it happens to me too.. --Jani On Sat, 5 May 2001, Andi Gutmans wrote: By the way, can you open a bug report about this? Please include PHP version, Web server setup and short reproducing script. At the same time if one of you guys can get an idea what broke this (or on what day) that would be great. You can do a binary search by checking out the PHP CVS by date. Andi At 06:58 PM 5/4/2001 -0400, Jon Parise wrote: On Fri, May 04, 2001 at 06:31:37PM -0400, Jon Parise wrote: ?php echo __FILE__; ? works fine here. Or do you meant something else, Chuck? The value is set; it's just missing all path delimiters. So if the file is actually /var/www/foo/bar.php, echo __FILE__ gives me varwwwfooobar.php. Which means that dirname(__FILE__) returns incorrect results. It's working fine here, too. Woops, scratch that. I see the problem now, too. It was introduced sometime between May 2nd (my last build) and today. Because now files in the Zend repository have changed in that window, I think it's probably a PHP bug. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] __FILE__ constant
On Sat, May 05, 2001 at 06:26:58PM +0300, Andi Gutmans wrote: Can you please try and check on what date (and maybe what patch) broke this? I'm pretty sure it happened after May 2nd, but I don't have an exact time. I quick scan of the cvs commit archives didn't turn up anything obvious, but I'm also not really sure where in the system this kind of anomaly would originate. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] __FILE__ constant
Can you check now? (update TSRM) At 18:46 5/5/2001, Jon Parise wrote: On Sat, May 05, 2001 at 06:26:58PM +0300, Andi Gutmans wrote: Can you please try and check on what date (and maybe what patch) broke this? I'm pretty sure it happened after May 2nd, but I don't have an exact time. I quick scan of the cvs commit archives didn't turn up anything obvious, but I'm also not really sure where in the system this kind of anomaly would originate. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- Zeev Suraski [EMAIL PROTECTED] CTO co-founder, Zend Technologies Ltd. http://www.zend.com/ -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] __FILE__ constant
On Sat, May 05, 2001 at 07:04:50PM +0300, Zeev Suraski wrote: That fixed the problem. Thanks! Can you check now? (update TSRM) At 18:46 5/5/2001, Jon Parise wrote: On Sat, May 05, 2001 at 06:26:58PM +0300, Andi Gutmans wrote: Can you please try and check on what date (and maybe what patch) broke this? I'm pretty sure it happened after May 2nd, but I don't have an exact time. I quick scan of the cvs commit archives didn't turn up anything obvious, but I'm also not really sure where in the system this kind of anomaly would originate. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] __FILE__ constant
It was a change in Zend (I'm nearly positive) that broke the __FILE__ constant. I've heard one person verify this and one person say it works for them; can people running latest cvs (and latest cvs of Zend, as well) say if it works for them or not? I tried to poke around in Zend a bit to see what might have done it, but it's a pain to look through histories without a cvsweb interface, and I didn't see anything obvious. It's probably something small, but it's severely breaking some of my code. Could a Zend guru take a look at it? Thanks, -chuck -- ...and remember: elmo is _not_ an insertion toy. -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] __FILE__ constant
Chuck Hagenbuch wrote: It was a change in Zend (I'm nearly positive) that broke the __FILE__ constant. I've heard one person verify this and one person say it works for them; can people running latest cvs (and latest cvs of Zend, as well) say if it works for them or not? ?php echo __FILE__; ? works fine here. Or do you meant something else, Chuck? -- sebastian bergmann[EMAIL PROTECTED] http://www.sebastian-bergmann.de bonn.phpug.de | www.php.net | www.phpOpenTracker.de | www.titanchat.de -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
Re: [PHP-DEV] __FILE__ constant
On Fri, May 04, 2001 at 06:31:37PM -0400, Jon Parise wrote: ?php echo __FILE__; ? works fine here. Or do you meant something else, Chuck? The value is set; it's just missing all path delimiters. So if the file is actually /var/www/foo/bar.php, echo __FILE__ gives me varwwwfooobar.php. Which means that dirname(__FILE__) returns incorrect results. It's working fine here, too. Woops, scratch that. I see the problem now, too. It was introduced sometime between May 2nd (my last build) and today. Because now files in the Zend repository have changed in that window, I think it's probably a PHP bug. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
