Re: __FILE__ constant
| From: | Andi Gutmans | Date: | Sat, 05 May 2001 14:29:02 +0000 |
| Subject: | Re: __FILE__ constant | ||
| References: | 1 2 3 4 5 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-53999@lists.php.net to get a copy of this message | ||
At 06:58 PM 5/4/2001 -0400, Jon Parise wrote:
On Fri, May 04, 2001 at 06:31:37PM -0400, Jon Parise wrote: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? Andifile is<?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 theactually /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.