Edit report at https://bugs.php.net/bug.php?id=42516&edit=1
ID: 42516
Comment by: pmugane at gmail dot com
Reported by: michael at zedeler dot dk
Summary: __FILE__ resolves symlinks
Status: Not a bug
Type: Feature/Change Request
Package: Scripting Engine problem
Operating System: Linux
PHP Version: 4.4.7
Block user comment: N
Private report: N
New Comment:
Really concerned about how this whole process has been ignored.
If __FILE__ is intended to resolve symlinks by design then provide a way to get the directory of the
symlink - it's really not that hard.
Seriously, it's been over a decade and this is still unresolved.
Previous Comments:
------------------------------------------------------------------------
[2013-01-24 15:21:52] michael at zedeler dot dk
I agree that this isn't a bug. I filed it as a change/feature request. Please revert.
------------------------------------------------------------------------
[2013-01-23 19:01:16] pajoye@php.net
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to
report
a bug at http://bugs.php.net/how-to-report.php
It is required by require_once and include_once, along other things (realpath
cache). It always been like that.
------------------------------------------------------------------------
[2013-01-23 17:36:39] ale dot comp_06 at xox dot ch
On development server I often have symlinked directories to common libraries.
It would be wonderful to have an option for the behavior of __FILE__ and allow it to return the non
resolved path if the developer wishes so.
Generally speaking, having some paths automatically "resolved" and some not, is very
disturbing. As far I can tell, all paths should be unresolved and one should use
"resolve_path()" to get the "real" path. A central switch should allow to get
all the paths resolved if one wants so (or the other way: the default being the paths being resolved
and the switch makes them unresolved).
------------------------------------------------------------------------
[2012-06-15 07:43:47] daniele dot segato at gmail dot com
This bug was open since 2007
would you mind assigning it to someone for fixing or discuss why you are leaving
it open?
maybe someone out there can help you
thank you
------------------------------------------------------------------------
[2012-04-06 17:28:55] bjori@php.net
I don't know why this was assigned to me
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=42516
--
Edit this bug report at https://bugs.php.net/bug.php?id=42516&edit=1