require_once() vs require()

[Hganavak]

Hi all,

Just a little question from me, why would you ever use require_once() when you can use require()? Even if you only require the file once, wouldn't it still just be easier to use require()? Is there any advantage to using require_once(), eg it uses up less memory?

Any help is greatly appreciated,
Cheers,
Hganavak.

[laserlight]

The point of require_once is that if you actually include the file more than once, it is still included only once. So if you say, define functions and/or classes in the included file, all would be fine.

[sagee]

when you got a bunch of included files, if you will have a require command in one of them similiar to a require command in the parent page you will ecncounter an erro due to the fact of double declaration, but if you have require_once then if their is a previous request to require this command is ignored.

so as you can see, it can help you out in a situation when you got couple of included file & there are require statments inside them.

[Horizon88]

Require() is faster, though, so if you're sure you don't need to check for previous requires, you should just use require(), not require_once().

[Hganavak]

Thanks for all your help guys, this forum is great. You'll be seeing plenty of me from now on, I feel sorry for you already :evilgrin:

[laserlight]

No problem 🙂
Remember to mark this thread as resolved with the thread tools.