Desired addon structure for modules

[daylesan]

If I wanted to create a module for an addon, and said module controlled whether or not (or how) some of the addon's functions execute, which would be the best approach?

Say I have this in my addon:

function MyFunction(arg1, arg2)
    if arg1 and arg2 then
          -- do stuff
    end
end

If the module is running, I basically want the whole thing to behave behave as if it had the following code:

function MyFunction(arg1, arg2)
    if arg1 and arg2 and not someVar then
          -- do stuff
    end
end

Should I use hooks for this? Are hooks viable once there are multiple modules that all want to influence how MyFunction executes?

Is it better to put the conditions from MyFunction into a table to which my modules can add/remove their own code as required?

Or create a dummy someVar that only changes if modified by the module?

What is generally considered to be the best approach?

[Xinhuan]

Don't use hooks. It will screw up once you allow users to enable/disable modules in game on demand.

Instead, create an table that will contain functions that modules can register and unregister with the main addon. The main addon then iterates through all registered functions in the table and calls each one in turn.

local funcs = {}
function MyAddon:RegisterModuleFunc(modulename, func)
    funcs[modulename] = func
end

function MyAddon:UnregisterModuleFunc(modulename)
    funcs[modulename] = nil
end

function MyAddon:MyFunction(arg1, arg2)
    for moduleName, moduleFunc in pairs(funcs) do
        -- Do stuff
        moduleFunc(arg1, arg2)
    end
end

Something like that, you can be fancier, have more arguments, have different tables, etc.

[daylesan]

Thanks for the excellent answer.