-
Key: IDL4CPP-35
-
Status: open
-
Source: Remedy IT ( Johnny Willemsen)
-
Summary:
The mapping says "IDL strings shall be mapped to C++ std::string, or to a type named omg::types::string that delivers std::string semantics", but when I now have CORBA and use an interface with operation "void set_string (in string text);", what is now the C++ signature I have to override in my servant implementation, it could be "void set_string(const std::string& text) override;", or "void set_string(const omg::types::string& text) override;" which could lead to portability issues when some vendor uses std::string and another omg::types::string. For defining data it doesn't make a real difference, but it is a problem when using CORBA
-
Reported: IDL4-CPP 1.0b1 — Thu, 25 Jan 2024 12:07 GMT
-
Updated: Tue, 9 Apr 2024 00:01 GMT
IDL4CPP — String mapping
- Key: IDL4CPP-35
- OMG Task Force: IDL4 to C++ Language Mapping (IDL4-CPP) 1.0 FTF