require_onces / require in modules

[Nightborn]

If you use the require_once / require functions please use them where there have most effect...

Do not use them at the start of your module outside of every function *unless* you need the functions it will provide or the code it contains in every single function of your module (means in the get_info, the do_hook, the _run) which is very unlikely.

Use them at best where you need them.
I.e. if you have 3 cases where one will affect alignment call the require_once("modules/alignment/func.php"); just in this case and leave the others out.

You will save ressources this way and the module gets more slim.

Thanks =)

[GenmaC]

It's also important to note that using include_once or require_once is almost always better than the alternative.

If you have two seperate modules hooking on the same hook and both are require("lib/systemmail.php") for instance, you will get a "cannot redefine function systemmail" error - so you'd want to use require_once instead of just require.  If you are distributing your module you'd almost definetely want to use require_once instead of require in case someone else was requiring the same lib on that hook.

[Adept]

yeah always use "_once"
only one exception where you can't

when there is code you need in the required module that is NOT wrapped in a function and it runs more than once in your module. this is in almost all cases a very poor programming practice and i have never seen a core module that does this.