In C++ I personally prefer using constants or enums over pre-processor defines when all it should do is represent a constant value. The end result is the same, but usually the compiler and debugger handles enums and constants better than pre-processor defines.

Regardless of my preferences, while you can use a pre-processor for angelscript too, it will not work for the registered function signatures (unless you modify the library to invoke the pre-processor when the default argument expression should be compiled). So, when registering a method/function with AngelScript that uses C++ pre-processor defines in the default arguments you need to translate these to something that AngelScript understand when informing the function signature. That can be either including the literal value, or it could be to register an enum first which can then be used in the default arg.