You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now you must use the Function<&MyClass::myFunction> {} and Field<&MyClass::myField> {} breeder templates to register members on a native class. This change was made to mitigate an issue with implicit conversions from static member function pointers to void * and the subsequent incorrect registration as a void * field. This can be properly mitigated using CX::IsFunction, without the API boilerplate of breeder templates.
Note: the Constructor<MyClass, [Args...]> {} breeder template is still required to register constructors for native classes.
The text was updated successfully, but these errors were encountered:
Matthewacon
changed the title
Remove FakeJni::_CX::Field and FakeJni::_CX::Function for native class member registration
Remove FakeJni::Field and FakeJni::Function for native class member registration
Oct 22, 2019
Right now you must use the
Function<&MyClass::myFunction> {}
andField<&MyClass::myField> {}
breeder templates to register members on a native class. This change was made to mitigate an issue with implicit conversions from static member function pointers tovoid *
and the subsequent incorrect registration as avoid *
field. This can be properly mitigated usingCX::IsFunction
, without the API boilerplate of breeder templates.Note: the
Constructor<MyClass, [Args...]> {}
breeder template is still required to register constructors for native classes.The text was updated successfully, but these errors were encountered: