RE: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.
From: Brian Tanner Date: Mon, 09 Jul 2001 00:23:24 +0000 Subject: RE: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0. References: 1 Groups: php.dev Request: Send a blank email to php-dev+get-59227@lists.php.net to get a copy of this message
-1 ;) I think it could make thing much more difficult and confusing actually. I like to keep all my include files in a central place, and define a constant __IncPath, where __IncPath is something like: $Document_Root."libraries/" That way I always just: include(__IncPath."foo.php"); include(__IncPath."bar.php"); I guess this might not be the best in all situations, but I find it makes my code more portable. Define one constant, and all is well. Although for newer users, you guys are probably very right. Makes things much easier when learning. So I guess as long as it doesn't add to ambiguity (would there be include_relative() or include($FilePath[,boolean relative])... could be useful. -Brian Tanner -----Original Message----- From: Andi Gutmans [mailto:andi@zend.com] Sent: July 8, 2001 9:15 AM To: php-dev@lists.php.net Subject: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0. Hey, I think one thing that bothers PHP developers is when they do: include "../foo.inc"; and in foo.inc they do: include "bar.inc"; That bar.inc is not searched for in foo.inc's current directory automatically. As we pretty much always have the expanded filename of the current executing script I thought it would be nice to add that if bar.inc is not found in the include_path to take the full path of foo.inc (i.e. /path/to/foo_inc/foo.inc) and try opening /path/to/foo_inc/bar.inc. What do you guys think? Andi -- 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
Thread (36 messages)
- Re: Possible feature for current version of PHP orPHP 4.1/5.0.
- Re: Possible feature for current version of PHP or PHP4.1/5.0.
- RE: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.
- Re: Possible feature for current version of PHP orPHP 4.1/5.0.
- Re: Possible feature for current version of PHP or PHP 4.1/5.0.
- Re: Possible feature for current version of PHP or PHP 4.1/5.0.
- Re: Possible feature for current version of PHP or PHP 4.1/5.0.
- RE: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.
- Re: Possible feature for current version of PHP or PHP 4.1/5.0.
- Re: Possible feature for current version of PHP orPHP 4.1/5.0.
- Re: Possible feature for current version of PHP or PHP 4.1/5.0.
- Re: Possible feature for current version of PHP or PHP 4.1/5.0.
- Re: Possible feature for current version of PHP or PHP 4.1/5.0.
- Re: Possible feature for current version of PHP or PHP 4.1/5.0.
- Re: Possible feature for current version of PHP or PHP4.1/5.0.
- Re: Possible feature for current version of PHP or PHP 4.1/5.0.
- RE: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.
- RE: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.
- RE: [PHP-DEV] Possible feature for current version of PHP or PHP 4.1/5.0.
- Re: Possible feature for current version of PHP orPHP 4.1/5.0.
- Unknown Message
| « previous | php.dev (#59227) | next » |
|---|