Repository navigation
Release v1.1.2
-
Add a macro switch for user to determine whether support volatile class objects
(access members by a volatile qualified class object, pointer or smart pointer). -
- Do not support this by default.
-
- Could add a macro definition
PEACALM_LUAW_NEED_VOLATILEto support it during compilation.
- Could add a macro definition
-
By default, when registering fake member variables, the type declaration for the first argument could be
const Obj*, notconst volatile Obj*required anymore, of course, if the macro switch for volatile class objects is not enabled. -
- Of course, using
auto *is still ok.
- Of course, using