Haxe for javascript without global namespace pollution?

Question

This question only applies to Haxe version < 2.10

I\'ve known about haxe for a while, but never really played with it until yesterday. Being curious,

Answer 1

I use the namespace switch on the compiler to clean those global root types up.

Answer 2

Haxe is not meant to be used for writing an isolated reusable component in a javascript web application. This is evidenced by the fact that the compiler emits standard library for every goddamn compilation. Most optimal use of javascript target is to write an application entirely in haxe and call external stuff using untyped blocks hoping it won't break anything. You should treat haxe output like a flash clip, oblivious to the environment it runs in, assumes it is the only thing running.

Or you might try wrapping the code with a with() block.

Answer 3

there's a namespaced (experimental) haxe compiler here http://github.com/webr3/haxe

Answer 4

The JSTM JavaScript generator macro optimizes haxe output in a number of ways:

1. the javascript output is split into seperate files per type
2. these files are optimized
3. a loader script loads the required types asynchronously
4. only one global variable is used: jstm
5. only code that is actually required to run your app is downloaded
6. new types can be loaded at runtime which makes possible highly scalable apps

check out http://code.google.com/p/jstm/ for more info.