Re: __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=1&id=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 (jon@csh.rit.edu) . 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: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net