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
The docs state that "Classes derived from scapix::bridge::object are bridged by reference and supported in Scapix bindings only when passed as std::shared_ptr" -- I thought that this means one has to wrap scapix::bridge::object-derived classes into std::shared_ptr in bridged methods both when such classes are returned or used as parameters. However, I found that methods containing scapix::bridge::object-derived parameters passed by value or const reference also get included in the generated bridge (I tested Java) even though std::shared_ptr is not used. Is this a feature that can be reliably used? If so, it would be nice to have this documented more clearly.
The text was updated successfully, but these errors were encountered:
The docs state that "Classes derived from
scapix::bridge::object
are bridged by reference and supported in Scapix bindings only when passed as std::shared_ptr" -- I thought that this means one has to wrapscapix::bridge::object
-derived classes intostd::shared_ptr
in bridged methods both when such classes are returned or used as parameters. However, I found that methods containingscapix::bridge::object
-derived parameters passed by value or const reference also get included in the generated bridge (I tested Java) even thoughstd::shared_ptr
is not used. Is this a feature that can be reliably used? If so, it would be nice to have this documented more clearly.The text was updated successfully, but these errors were encountered: