But like you see, it's slowly getting there ;)
So why not start using them?
As for the rest... I didn't question your need for a smart pointer. I questioned the need for wrapping your critical...
Type: Posts; User: Elysia
But like you see, it's slowly getting there ;)
So why not start using them?
As for the rest... I didn't question your need for a smart pointer. I questioned the need for wrapping your critical...
I would avoid Borland C++. It is obviously not very good compared to other free compilers (such as GCC and Visual C++ which both have C++0x support).
I was merely wondering how you intended to use...
So you are using some compiler that is not Visual C++ or GCC?
DLL exports make things slightly more complicated, but the basic idea would be the same. You just have to make sure that the...
The way I see it, there are two solutions:
1) Use pointers with exclusive ownership and store them in the map. Wait until all threads terminate before clearing the map. if you then populate the...
All the operations on the block pointer and any of its data must be atomic, because several threads can access them at once. If you make sure they're atomic, there should be no problems that I can...
The best bet, I think, is simply to create a new smart pointer for thread B. This will avoid racing conditions without additional coding. You could add debug statements to "lock" a shared pointer to...