Bug #12203 Updated: Inconsistent __FILE__ contents when using require/require_once

ID: 12203 Updated by: yohgaki Reported By: adam@iewebs.com Old Status: Open Status: Analyzed Bug Type: Scripting Engine problem Operating System: Linux PHP Version: 4.1.0 New Comment: I think __FILE__ is better to set filename that is requested. Status = Analyzed Previous Comments: ------------------------------------------------------------------------ [2001-12-12 08:21:13] yohgaki@php.net PHP Version update ------------------------------------------------------------------------ [2001-12-12 07:02:26] yohgaki@php.net On my linux with 4.1.0, __FILE__ has always actual /path/to/file. (i.e. not pathname of sym link, but pathname linked to) It does not ommit path, though. I think __FILE__ should have pathname for sym link instead of pathname linked to... Is this correct behavior? Anyone? ------------------------------------------------------------------------ [2001-07-17 08:20:14] adam@iewebs.com Not sure if this is a bug or a feature, or what the correct result should be, but... Related to bug #6636, require_once() and include_once() used on a soft link will result in the __FILE__ constant containing only the filename of the link, whereas include() and require() will result in __FILE__ containing the full path and filename of the linked file. ln -s /path/to/file.php /path/to/link.php CASE ONE: require_once('/path/to/link.php'); // returns 'link.php' echo __FILE__; CASE TWO: require('/path/to/link.php'); // returns '/path/to/file.php' echo __FILE__; ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=12203&edit=1