[optional] Where are the fixes for self-assignment problem?
Several weeks ago I reported that boost::optional<T> was not safe under self-assignment. The author of the class said he was fixing the library, but no new versions of the code have been checked into the CVS repository. With the code freeze for boost 1.33 only a couple of weeks away, I was wondering whether optional<T> would be fixed on time. Joe Gottman
"Joe Gottman" <jgottman@carolina.rr.com> escribió en el mensaje news:d2p5rl$6r3$1@sea.gmane.org...
Several weeks ago I reported that boost::optional<T> was not safe under self-assignment. The author of the class said he was fixing the library, but no new versions of the code have been checked into the CVS repository. With the code freeze for boost 1.33 only a couple of weeks away, I was wondering whether optional<T> would be fixed on time.
Hi Joe, I haven't commited the fixes yet. The reason is that I found an issue with references and I couldn't make up my mind about how to fix it. See this thread: http://lists.boost.org/MailArchives/boost/msg79670.php I will reach a dicision soon enough though. Best Fernando Cacciola
participants (2)
-
Fernando Cacciola -
Joe Gottman