Difference between revisions of "Loading Order of Lua Files"
From GiderosMobile
(added see also) |
(added example) |
||
Line 20: | Line 20: | ||
'''This is very useful if you develop a Lua library that is meant to be used in several projects.''' | '''This is very useful if you develop a Lua library that is meant to be used in several projects.''' | ||
+ | |||
+ | === Example === | ||
+ | <source lang="lua"> | ||
+ | --!NEEDS:luashader/luashader.lua | ||
+ | |||
+ | local function makeEffect(name,vshader,fshader) | ||
+ | ... | ||
+ | end | ||
+ | </source> | ||
=== See also === | === See also === |
Revision as of 01:40, 26 September 2020
Supported platforms:
Available since: Gideros 2020.5
Description
You can now implement Gideros Code Dependency by code instead of Gideros project setting.
--!NEEDS:your_file.lua
This will tell Gideros to load your_file.lua before the file containing the above code.
To tell Gideros the file should not be executed/parsed right on start but will be loaded through a require or a loadfile command, you can write:
--!NOEXEC
This is very useful if you develop a Lua library that is meant to be used in several projects.
Example
--!NEEDS:luashader/luashader.lua
local function makeEffect(name,vshader,fshader)
...
end
See also
Methods |
EventsConstants |