[mtasc] Different way of saving classes

[David Rorex]

Also the statement 'new a.b.c.d()' would be replaced with 'new a_b_c_d()'
But I would think in most applications, 'new ...' is not called in
performance critical loops or anything.

Also, implementing this would break compatibility with swfs compiled with MMC.
(ie: a mtasc swf has class a.b -> a_b, and loadMovies() a mmc swf,
which calls 'new a.b()' and it will fail to find it)

-David R

On 9/12/05, Ralf Bokelberg <info at bokelberg.de> wrote:
> Which kind of statements, beside the obvious access to static members,
> are boosted by this hack? Can you tell us?
> 
> Cheers,
> Ralf
> 
> 
> Martin Heidegger wrote:
> 
> > In contrast to Flash the Flex compiler doesn't safe the classes in
> > globale like
> >
> > _global.org.domain.MyClass
> >
> > but like
> >
> > _global.org_domain_MyClass
> >
> > I thought about why they might have changed that and came to result
> > that this has to be faster than the "." syntax, because this way no
> > scope change occurs. I can imagine that this is defacto a big
> > performance boost for OOP applications. Is it possible to make Mtasc
> > working like this?
> >
> > yours
> > Martin.