Jump to content

Recommended Posts

can someone help on this please

 

include("config.php");
include("includes/user_info.class.php");

 

require_once("config.php");
require_once("user_info.class.php");

 

This both thing does the same thing, but which one is better to use any ideas ???

 

I got this from the manual but could not understand....

 

The documentation below also applies to require(). The two constructs are identical in every way except how they handle failure. include() produces a Warning while require() results in a Fatal Error. In other words, use require() if you want a missing file to halt processing of the page. include() does not behave this way, the script will continue regardless. Be sure to have an appropriate include_path setting as well. Be warned that parse error in included file doesn't cause processing halting in PHP versions prior to PHP 4.3.5. Since this version, it does.

 

 

Link to comment
https://forums.phpfreaks.com/topic/71919-solved-help-on-include/
Share on other sites

Your script will stop if config.php can't be included if you use require(), for any reason. Ie it doesn't exist or PHP doesn't have privs to read the file.

 

include() will issue a warning if config.php cannot be included, but will continue running the script.

 

Use require() for vital files, and include() for other non-vital things.

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.