>> No it doesn't, because haXe classes are put in the
current Movieclip and
>> not in _global, so we don't have to jump at the end
of their definition
>> if they exists already.
>
> Not sure I understand you here. I've tried this in
haXe (and maybe this
> starts to belong on the haXe list...):
>
> class X = { static var e = [ /* about 44K elements */
]; }
>
> and haXe fails with
IO.Overflow("write_ui16").
>
> So it looks like both mtasc and haXe have the problem.
????
Uhm, yes, but this actually a distinct problem.
haXe wraps all statics initialization around a try...catch
block that
displays uncaught exceptions on initialization. And there is
another
limitation which is of 64KB of bytecode in a try expression.
However,
what you can do is store your data into text file, then link
it with
haXe using -resource (see http://haxe.org/tutos
/resources tutorial).
Nicolas
--
MTASC : no more coffee break while compiling
|