We came across this issue in one of our applications with clang 3.5.0.
The following code compiles just fine in "C++03" mode, but fails in
"C++11" mode. Is clang right here, or is it a compiler bug? Note that
the work around (commented out below) is pretty simple and works in
both modes, but I'm n
On Thu, 23 Oct 2014, John Peterson wrote:
> We came across this issue in one of our applications with clang 3.5.0.
> The following code compiles just fine in "C++03" mode, but fails in
> "C++11" mode. Is clang right here, or is it a compiler bug?
http://www.cplusplus.com/reference/ios/ios/opera
On Thu, Oct 23, 2014 at 10:50 AM, Roy Stogner wrote:
>
> On Thu, 23 Oct 2014, John Peterson wrote:
>
>> We came across this issue in one of our applications with clang 3.5.0.
>> The following code compiles just fine in "C++03" mode, but fails in
>> "C++11" mode. Is clang right here, or is it a co
On Thu, 23 Oct 2014, John Peterson wrote:
> OK, so you are saying this code
>
>> bool t = (is >> val);
>
> is legal? (FWIW, it works with g++ -std=c++11)
I believe it's legal in C++11. istringstream inherits operator>> from
istream; that returns a reference-to-istream. That istream should
the
