Eventually backwards compatibility has to be broken anyway. If the Level
changes, then that would be a good time to switch over to
standard(std/boost) smart pointers as well, which may break other code that
depends on Object. For the most part I don't think this will have a large
impact on
I think mixing smart pointers and static class allocation would just mix
things up. We should instead choose when to use one over the other.
We are currently returning new, dynamically allocated level objects for
each call to getInfo() etc. This memory must be freed. When logging from
a
Choosing between the smart pointers should be pretty straight forward:
http://stackoverflow.com/questions/7095556/how-to-handle-evolving-c-std-namespace-e-g-stdtr1shared-ptr-vs-std
This way people can use either a boost pointer or a C++11 pointer depending
on their compiler. I only suggested
Guten Tag Robert Middleton,
am Donnerstag, 27. Oktober 2016 um 01:39 schrieben Sie:
> I haven't delved too deeply into the code(I don't have time today),
> but it looks like all that Object is doing is providing Java-like
> garbage collection in terms of memory management.
That was my
