FOSS gamedev and creative worlds

Hi community,
I just wondered wheter a function defined in Mod X can be accessed from Mod Y...

Here's what I mean:

Mod X
Mod Y:

Yes. It is in this format:

ModX:


ModY:

Traxie21 wrote:Yes. It is in this format:

ModX:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

function testfunc()
 print("Hello World")
end


ModY:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

ModX.testfunc()


Wow, that's very good. This would add some more stuff to my PHP-Server-Manager. It would automatically install a mod which provides some functions to interact with my Server-Manager, such as notifications :D

THX

Traxie21 wrote:Yes. It is in this format:

ModX:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

function testfunc()
 print("Hello World")
end


ModY:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

ModX.testfunc()


Wrong. The version in the first post is correct. All mods run in the same Lua environment, so they share a global namespace. One cant access functions/variables that are local, tough.

PilzAdam wrote:Wrong. The version in the first post is correct. All mods run in the same Lua environment, so they share a global namespace. One cant access functions/variables that are local, tough.

...which means, in turn, that when you declare a function in your mod, either you need to make it local, or you need to give it a very unique name, or do what I do and force it into a new namespace (e.g. plantslib:spawn_on_surfaces()).

That way, your function names don't conflict with anyone else's mods.

Uhm, now I'm confused... Which is the right way to access this "external" function?

webdesigner97 wrote:Uhm, now I'm confused... Which is the right way to access this "external" function?

The right way is simply call the function (as in the first post).
But its recommended to give the function a unique name, so that you dont conflict with other mods.
E.g. put all mods into one table:
ModA

ModB:

But again, this is only a recommendation.

PilzAdam wrote:

webdesigner97 wrote:Uhm, now I'm confused... Which is the right way to access this "external" function?

The right way is simply call the function (as in the first post).
But its recommended to give the function a unique name, so that you dont conflict with other mods.
E.g. put all mods into one table:
ModA

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

modA = {}

function modA.myEpicFunction()
    print("Works")
end

ModB:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

modA.myEpicFunction()

But again, this is only a recommendation.

Ok, now I understood :) Thank you very much!

If you declare a function in mod A, mod B can access that function by just calling it by name. So if in mod A you declare a function with a name like "printvars", mod B can just call it directly with no special preparations, e.g. printvars(foo, bar, blah, ...)

What you should do is declare it in a new namespace, e.g.

mymod:printvars = function(foo, bar, blah, ...)

and then call it with that name. Failing that, you could use underscores and just give it a descriptive name that's least likely to be confused with some other mod, e.g. mymod_print_vars_to_screen or something.

The bottom line is that you must always make sure your functions have unique, hard-to-conflict-with names if they aren't local.

ok. But I never worked with namespaces before. how do I declare them?

ok. But I never worked with namespaces before. how do I declare them?

Just like I wrote. In mod A, where you want the actual working code for your function to reside, you'd do this:

mymod:printvars = function(foo, bar, blah, ...)
...some code here...
...some code here...
...some code here...
end

and then just call mymod:printvars(foo, bar, blah) in your other mods. Obviously, the parameter names and how many you use are up to you. For a working example, look at my plantlife/plants_lib mod.

I suggest to simply dont listen to VanessaE here, because she just makes things too complicated. The : is used in Lua for object oriented programming, but you really dont need it here.

That seems a little harsh, but I agree that the colon isn't necessary here because you are expecting other modules to use your global variable to call the functions, rather than passing a reference different objects around. So you really don't need a reference to your object implicitly passed to each function call.



What we are talking about is the difference shown by this example, using the default API:



So what you are talking about is probably the first case where you simply call "mymodule.myfunction(...)".

On the other hand, if you want a function that is ONLY callable within the same file (NOTE: not the entire module, but the same actual *.lua FILE!), you want:



Which keeps it from conflicting with any other module that might use a function, variable, or object called "my_func".

Gaah. It would've been easier If I didn't copy-paste that first post. Forgot to edit the ModX part. Yes, I do know how it is supposed to work.

Thx @ all for your help! I'll try it out!