HOME Community Articles Code Library People Mail Archive My Account Contribute PHP Jobs

Open Source Database Feature Comparison Matrix Try Declarative Programming with Annotations and Aspects Locate All Stored Procedures and Their Objects/SQL Tables Building a Stored Procedure Generator Making Tables Read-only in Oracle

24-hour Support Daily Backup Dedicated Servers JSP/Java Servlets PHP MySQL Streaming Audio/Video Telnet/SSH Unix Hosting 24-hour Support

From: Bug Database (php-dev <email protected>)
Date: 11/25/99

• Next message: Andi Gutmans: "[PHP-DEV] Re: [PHP4BETA] Re: [PHP-DEV] Should php3_fopen_for_parser change the current working directory?"
• Previous message: Rasmus Lerdorf: "Re: [PHP-DEV] backtrace from segmentation fault"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

ID: 2700
Updated by: zeev
Reported By: pfaffman <email protected>
Status: Closed
Bug Type: Documentation problem
Assigned To:
Comments:

There shouldn't be any change in behavior from PHP 3.0 here,
it's the same code. In both versions, if you specify no
include_path at all, . (cwd) is assumed. But if you do
specify an include_path, . is no longer assumed, and you have to explicitly specify it in order for it to work.

Full Bug description available at: http://bugs.php.net/version4/?id=2700

-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: php-dev-unsubscribe <email protected>
For additional commands, e-mail: php-dev-help <email protected>
To contact the list administrators, e-mail: php-list-admin <email protected>

• Next message: Andi Gutmans: "[PHP-DEV] Re: [PHP4BETA] Re: [PHP-DEV] Should php3_fopen_for_parser change the current working directory?"
• Previous message: Rasmus Lerdorf: "Re: [PHP-DEV] backtrace from segmentation fault"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]