Thanks for pointing out that post. It is quite interesting. From what I see, however, Joshua was talking about consuming native extensions from Haxe. There is still no way to create those native extensions using Haxe. Of course, I could be wrong. It would be great if someone else who is more knowledgeable on this topic could explain.
Again, thanks for the feedback. I am very impressed by hxcpp's ability to compile Haxe code to C++. I have been playing around with that functionality, but it seems the tool is designed, as you said, to create complete applications, not native extension libraries. As a result, the compiled binaries contain a lot of unnecessary code. Most importantly, according to Adobe, the native extension library must implement the FREExtension interface and expose the public functions to AIR.
I understand that this may be too much to ask, but I really do believe that this is going to be a very useful feature. It allows developers to create and share awesome AIR native extensions without having to manage 3-4 different codebases.
I may be wrong about this, but from what I gather, the new AIR 3 allows developers to use native extensions, but Adobe did not provide any tools to help create these native extensions. I understand that these extensions can be created using standard C++ (or Java on the Android platform), but I suppose it would be nice to be able to use the haxe language to create them.
Now that AIR3 supports native extensions, I wonder if you are take advantage of Haxe NME to create those native extensions. I think it is the best way to fully realize the idea of "write once, deploy everywhere". How hard is it to implement this?