[mtasc] Strange build problem w/ ActionStep

[Nicolas Cannasse]

> Here is the issue. There is a class called ASTheme with a static method
> called current(). It returns the current theme...whatever that may be,
> or creates the default theme if current hasn't been set.

Depending on several things, such as the commandline order or file paths,
the order in which the classes are generated by MTASC might change. In that
case, it is possible that for example at the time you're calling current()
the class ASTheme is not yet defined : this will only happen if you're
calling current() from a static initializer. If you're sure that everything
is called from main() or later, it shoudln't cause any initialization order
problem.

Nicolas