ID: 7710
Updated by: jmcastagnetto
Old-Status: Open
Status: Closed
Bug Type: Documentation problem
Assigned To: 

change in behavior already documented in manual.

Previous Comments:

[2000-11-26 04:01:25] [EMAIL PROTECTED]
May I ask why this change was made?

I was wondering if you could help us find an alternate way -- we couldn't find one -- 
so please share the knowledge with those who couldn't find it easily like you! ;-)

Nonetheless, I can't imagine why functionality like what we're interested in isn't 
available in PHP. It seems like pretty basic stuff...



[2000-11-25 09:38:06] [EMAIL PROTECTED]
This is in fact a documentation issue.
PHP 4.0 changed the behavior of require(), and each separate file must now be parsable 
by itself.  It's a result of a fundemental change that took place between PHP 3 and 4, 
and this behavior will remain as is...

You'd have to find an alternative way of doing what you want (which should be fairly 

Doc team:  The documentation for require() is no longer close to being accurate for 
PHP 4.0 in general, and PHP 4.0.2&later in particular...  It's basically just like 
include() today, except it can't fail, and would bail out if it does.


[2000-11-20 05:31:18] [EMAIL PROTECTED]

<? require "header.php3"; ?>

sid is set

<? require "footer.php3"; ?>


        if (isset($sid))



                echo "sid not set";


[2000-11-20 05:28:02] [EMAIL PROTECTED]
This is not a documentation issue. Read this again before you respond so quickly.


[2000-11-09 09:52:30] [EMAIL PROTECTED]
Please read this manual page carefully:


Changed to Documentation problem as I couldn't 
find the incompatibilities list (for PHP 3 vs. PHP 4)
from the manual.



The remainder of the comments for this report are too long.  To view the rest of the 
comments, please view the bug report online.

ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to