ID: 42516
User updated by: michael at zedeler dot dk
Reported By: michael at zedeler dot dk
Status: Open
-Bug Type: Documentation problem
+Bug Type: Feature/Change Request
Operating System: Linux
PHP Version: 4.4.7
Assigned To: bjori
New Comment:
Wrong category.
Previous Comments:
[2009-04-23 17:53:20] michael at zedeler dot dk
Sorry to bug you again, but as I am writing in the report, just putting
a description of the errant behaviour is not a useful fix.
[2008-04-13 23:46:35] bj...@php.net
This bug has been fixed in the documentation's XML sources. Since the
online and downloadable versions of the documentation need some time
to get updated, we would like to ask you to be a bit patient.
Thank you for the report, and for helping us make our documentation
better.
[2007-09-01 21:02:38] michael at zedeler dot dk
Description:
__FILE__ does not return the path used to invoke the current file, but
resolves symlinks.
This behaviour is extremely problematics, since important information
is thrown away. The web is teeming with postings from people that are
experiencing problems because of this.
In http://bugs.php.net/bug.php?id=37603 this bug was mentioned and the
response was that it is intended behavior with a reference to the
manual.
The page
http://es.php.net/manual/en/language.constants.predefined.php
is the primary source of information for __FILE__, and it does not
mention resolving symlinks at all.
I'd like if we could have som kind of dialogue about how to solve the
problem, in stead of just having this bug being closed with a "Bogus"
status.
My suggestions are:
1) introduce a new magical constant that behaves as it should.
2) put a parameter in php.ini that changes how __FILE__ behaves.
Reproduce code:
---
This is basically a reopening of http://bugs.php.net/bug.php?id=37603
Expected result:
This is basically a reopening of http://bugs.php.net/bug.php?id=37603
Actual result:
--
This is basically a reopening of http://bugs.php.net/bug.php?id=37603
--
Edit this bug report at http://bugs.php.net/?id=42516&edit=1