Quote:
Originally Posted by xXziroXx
Definideatly alternative A.
|
No.
Definitely
Quote:
Originally Posted by contiga
Alternative C, which is:
PHP Code:
//Class - mud
//#CLIENTSIDE
function GetItemPower( itemid)
return ( @ "item-" @ itemid).power;
PHP Code:
//Some weapon
this.join( "mud");
//#CLIENTSIDE
function onCreated()
echo( mud::GetItemPower( 3324));
|
No.
B.
If you have >1 weapon all joining the same class (and I'm assuming there's more than one function in that class), it is less efficient to load each of those weapons with code that is unneeded for that weapon (say the weapon only uses one of many functions) using join() than to have each of these weapons calling a public function in a single existance of the library.
If that's the only function in the class, the different is negligible.