MissAllSunday/Breeze — comment on commit 8040759b4e5b0b7237e17c7b49b707475c2cddd8
File:  line 0
By norv:

Another option here would be to write wrapper functions, around the static methods calls.

i.e.
[code]
function BreezeAdminMain()
{
BreezeAdmin::Main();
}
...
// register BreezeAdminMain() for SMF to call
[/code]

That said, generally, it can be argued that static methods are not *that* different from functions. They don't give you any real advantages of object oriented programming *yet* (only a bit of encapsulation, and that's fine for a start), however they're a bit like the poor kid on the block comparing to using instance methods for the jobs (except the latter isn't really possible here, unless with a singleton).

It would be possible for SMF to use call_user_func_array() like it does for integration hooks, or to insert a forwarding function like the one you suggested elsewhere (and like this one in the example here).