Oh, and another topic -- if I change the interface of telemetry in Debug.cpp and need to detect that in hxtelemetry.hx, since I didn't put a version in to start with -- can I do something like:
Debug.cpp:
#define TELEMETRY_VERSION=2
Hxtelemetry.hx (@header or something):
#ifndef TELEMETRY_VERSION#define TELEMETRY_VERSION=1
Would this work with older (undefined) and newer (ver=2) hxcpp?
Or is there a different/better way to detect hxcpp version?
Hugh Sanderson [11:00 PM]
You can change toolchain/common-defines.xml to define HXCPP_TELEMETRY=2 if you like - this will be visible in the generated .cpp code
But not the .hx code
Jeff Ward [11:01 PM]
Can my HxTelemetry library be compatible with both versions?
Hugh Sanderson [11:02 PM]
It depends on if you need to change the haxe code
You could do something like inject "version=2" FROM the haxe code (via build.xml) and then check in Debug.cpp and do some kind of wrapepr for the old code
Notes from slack:
Oh, and another topic -- if I change the interface of telemetry in Debug.cpp and need to detect that in hxtelemetry.hx, since I didn't put a version in to start with -- can I do something like: Debug.cpp:
#define TELEMETRY_VERSION=2Hxtelemetry.hx (@header or something):#ifndef TELEMETRY_VERSION#define TELEMETRY_VERSION=1Would this work with older (undefined) and newer (ver=2) hxcpp?Or is there a different/better way to detect hxcpp version?
Hugh Sanderson [11:00 PM] You can change toolchain/common-defines.xml to define HXCPP_TELEMETRY=2 if you like - this will be visible in the generated .cpp code But not the .hx code
Jeff Ward [11:01 PM] Can my HxTelemetry library be compatible with both versions?
Hugh Sanderson [11:02 PM] It depends on if you need to change the haxe code
You could do something like inject "version=2" FROM the haxe code (via build.xml) and then check in Debug.cpp and do some kind of wrapepr for the old code
Jeff Ward [11:04 PM] Ok, thanks for the info!