Thanks again.

With one additional change, I was able to get all of test_feature to pass on my M1. It was just to change the expected test result in one case.

https://github.com/ramcdona/angelscript-mirror/tree/M1_test_difference​

Not sure if this is a M1 specific thing, or can be expected for all AS_MAX_PORTABILITY cases.

Theoretically, this should mean I should be able to get my program to work on M1 given some set of incantations for calling conventions, etc.

I spent a few hours with it last night and unfortunately I made no meaningful progress.

Is there any documentation that I'm missing? I really can't make heads or tails of when I'm supposed to use which macro - particularly with AS_MAX_PORTABILITY.

Rob

I'll have to fix that test. The content of the two lines that you changed shouldn't really be validated in the test, as this part of the debug output are for uninitialized variables and the values can be random.

The documentation for the calling conventions are here:

• What macro to use to get address of function or method: http://www.angelcode.com/angelscript/sdk/docs/manual/doc_register_func.html#doc_register_func_1​
• Calling conventions for native functions: http://www.angelcode.com/angelscript/sdk/docs/manual/doc_register_func.html#doc_register_func_2​
• Registering object types: http://www.angelcode.com/angelscript/sdk/docs/manual/doc_register_type.html​​
• Generic calling convention: http://www.angelcode.com/angelscript/sdk/docs/manual/doc_generic.html​
• Wrapper macros: http://www.angelcode.com/angelscript/sdk/docs/manual/doc_addon_autowrap.html​​