>> So if I remove the check when compiling a class
that contains just
>> static data like above, can I expect mtasc to
produce a good .swf?
>
> Yes.
>
> Nicolas
Thanks. However, when I remove the check, I still get an
error
from mtasc when the data is large, namely, an overflow in
write_i16. For my particular case when my array has 715
elements
it compiles and when my array has 716 elements it does not
compile
(it gets the write_i16 overflow).
Is this an issue with the Flash format or is it particular
to mtasc?
I am of course generating the data by a program, so I could
arrange
to split it up into multiple classes if necessary. If
anyone has
a favorite way of solving the problem please post.
Also, is haXe a solution -- does haXe have the same
limitations when
generating .swf?
Regards,
Trevor
--
MTASC : no more coffee break while compiling
|