Dan Korostelev

- HAXE_STD_PATH - specifies path to the haxe `std` library (used by haxe itself) - HAXELIB_PATH - specifies path for haxelib libraries (used by haxelib) - HAXEPATH - specifies path...

That makes sense. Do we have target-detals chapters yet? I would document this stuff, but I'm not sure about what the manual structure should be.

I added some info on `@:jsRequire`. Still need to document `@:pythonImport` so I leave this issue open.

I'm not sure yet. I don't like the `ignoreErrors` argument for `@:pythonImport`...

We're talking about [this page](https://haxe.org/manual/expression-switch.html), right? It contains this sentence: > Case body expressions never "fall through", so the break keyword is not supported in Haxe. I think we could...

ping @waneck

@waneck I tried to document these in https://gist.github.com/nadako/c225caf5fde5cee5dcd4#using-custom-net-distribution. Could you please review and confirm that this can go into HaxeManual (see #138)? Also, what `@std` postfix in `-net-lib` does again?

How about Haxe (.hx)? :)

But `hxnodejs` doesn't implement full sys api (because it's impossible without dirty tricks (#64). It just implements some of it, so I don't know if it's reasonable to define `sys`...

the main problem is that we can't implement synchronous API that are used in sys, like `Sys.stdout()`.