Hi,
I was in the process of summarizing to myself my understanding of the
throwing move constructors issue that we have for C++0x, and it occurred
to me that possibly the existing attribute nothrow in G++ behaves
exactly as noexcept(true) in Dave' and Rani' N2983 (or, per that paper,
the M$ behavior for throw(), not conforming but better from the
optimization point of view). I even suspect Honza was hinting at this
when he added the decorations a while back... Anyway, if somebody can
confirm that, I believe that the above mentioned decorations should
actually use unconditionally the attribute instead of throw(), in C++
mode too, that is.
Hints?
Thanks,
Paolo.