Open GoogleCodeExporter opened 9 years ago
Hmm. Unfortunately, the replacement for auto_ptr is unique_ptr, which is a
C++11 feature, and I'm not ready to require C++11 for the library (I mean,
there aren't any compilers yet that even fully support it, and there are plenty
of yaml-cpp users on older compilers and can't upgrade).
Do you have a patch to silence the warning?
Original comment by jbe...@gmail.com
on 5 Nov 2012 at 2:41
How about a #define to use unqiue_ptr on C++11 compliant compilers?
Original comment by tent....@gmail.com
on 27 Nov 2012 at 5:57
Perhaps. But the semantics of unique_ptr and auto_ptr are a little different,
so it wouldn't just be a drop-in replacement.
Original comment by jbe...@gmail.com
on 27 Nov 2012 at 2:15
Original issue reported on code.google.com by
Vladimir...@gmail.com
on 5 Nov 2012 at 2:33