So then logic says that if all of our stuff is in org.apache.flex,
that will always be reduced, at least from my compiler experience that
is how I would do it.
Ok, then not to worry, we can even tests this sooner than later to see
exactly what the closure compiler does with our namespaces.
Mike
Quoting Erik de Bruin <e...@ixsoftware.nl>:
'goog' seems to be the reasonable way to go. I would be a bit concern
about name-space implementation yet.
org.apache.data.blah.foo is the major bottleneck. And currently not that
different from haxe approach. Even after closure compiler heavy lifting it
is still
a.b.c.d.e.f. It starts with "org.apache.data.blah.foo" as a string , so
why not ns_orgApacheDataBlahFoo that will get complied to 'abcdef'
? Just an
idea.
Stop worrying: the Closure Compiler (which the "goog" approach uses)
is specifically designed to handle stuff like those "deep" namespaces.
It checks dependencies, so it knows what it can and cannot rename, and
it checks for collisions when doing the renaming. The result of all
this is that you can during development use namespaces however deep
you like - "this.is.a.really.deep.namespace.dont.you.think - but if
the Closure Compiler figures it can get away with it, it will
ruthlessly refactor that to: "a".
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
