Not sure if this is the right place for it, but...
Just idly looked at the latest Haxe release info in passing on Hacker News (I've never actually used it), and noticed this:
Improved C++ code output
While Haxe tries to create the most optimal code for each target, reading through the output code can be hard sometimes. Our Haxe C++ target maintainer Hugh did a great job in making the output noticeably cleaner. It is now much easier to make the connection between original Haxe and generated C++ code, since the latter is annotated with the corresponding Haxe line numbers via HXLINE():
I think HXLINE is probably a no-op macro something like this, or gets converted into "" (if macros can do that!).
Thought it might be something worth looking at, whether for allowing manual cross-referencing between .mx2 and output, or perhaps, even better, it might even help with debugging, taking (eg.) C++ debugger output and referencing it back to the .mx2 source in the Ted2 debug output.
Original Author: DruggedBunny
Not sure if this is the right place for it, but...
Just idly looked at the latest Haxe release info in passing on Hacker News (I've never actually used it), and noticed this:
I think HXLINE is probably a no-op macro something like this, or gets converted into "" (if macros can do that!).
Thought it might be something worth looking at, whether for allowing manual cross-referencing between .mx2 and output, or perhaps, even better, it might even help with debugging, taking (eg.) C++ debugger output and referencing it back to the .mx2 source in the Ted2 debug output.