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
Added argument_implementation_type attribute to mapped types, and to function and method arguments
It is valuable for callbacks, when a method has std_string argument which has implementation_type="std::string".
Bcapi generates the following template for callback implementator:
...
virtual void f1(std::string arg1)...
...
however, the base user class accepts only const std::string&:
...
virtual void f1(const std::string& arg1) = 0;
...
which causes problems.
The text was updated successfully, but these errors were encountered:
PetrPPetrov
changed the title
Added argument_implementation_type attribute to mapped types, and to function and method arguments
Add argument_implementation_type attribute to mapped types, and to function and method arguments
Nov 1, 2018
Added argument_implementation_type attribute to mapped types, and to function and method arguments
It is valuable for callbacks, when a method has std_string argument which has implementation_type="std::string".
Bcapi generates the following template for callback implementator:
...
virtual void f1(std::string arg1)...
...
however, the base user class accepts only const std::string&:
...
virtual void f1(const std::string& arg1) = 0;
...
which causes problems.
The text was updated successfully, but these errors were encountered: