On 13-Sep-08, at 07:45 , Daniel Luis dos Santos wrote:
That said, STL can be used only within a library's own code. Then
when coding a shared library one must implement all kinds of data
structures that can be used at the boundary. Isn't that like
reinventing the wheel ?
Yes. But that is
On Sep 12, 2008, at 11:21 AM, Daniel Luis dos Santos wrote:
The problem was that in CVDisplayPipeline.h I was declaring the map
as a return type of a method, but without specifying the template
types (caused by my relative ignorance of C++).
Now I have another problem, which I wonder if yo
On Sep 12, 2008, at 1:17 AM, Daniel Luis dos Santos wrote:
I have std::map *var as a member variable of the ObjC class.
Is this really how it's declared? std::map is a template, so you have
to do something like:
std::map* var;
Or better yet:
typedef std::map my_map_type;
...
The problem was that in CVDisplayPipeline.h I was declaring the map as
a return type of a method, but without specifying the template types
(caused by my relative ignorance of C++).
Now I have another problem, which I wonder if you could help :
On one project I have a target that builds a sh
On 12 Sep 2008, at 10:17, Daniel Luis dos Santos wrote:
Hello !
I have an objective C class and want to call a method on a class in C
++. As argument to the C++ class is a map instance of the STL.
The ObjC class definition is on a file with a mm extension.
I have std::map *var as a member v
Hello !
I have an objective C class and want to call a method on a class in C+
+. As argument to the C++ class is a map instance of the STL.
The ObjC class definition is on a file with a mm extension.
I have std::map *var as a member variable of the ObjC class. When I
compile the code there
