Étienne Mollier <emoll...@emlwks999.eu> writes: > I believe in the case of anfo, that warnings about auto_ptr / > unique_ptr are red herrings. If I search for "error:"s, then I > get some errors about no match for operator<:
Oops, good catch. As for unique_ptr, this is evidently one of those situtations where whoever makes the substitution (possibly upstream after all at some point) will need to make additional changes to make it clear that their usage is safe. In particular, the ...Reader constructors will probably want to accept auto_ptr<> by rvalue reference rather than by value: std::unique_ptr<google::protobuf::io::ZeroCopyInputStream>&& is -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
