Xcode/cout/complex problem

Question

Level 1

0 points

Xcode/cout/complex problem

Hi,

I have tried a few fora with this query and so far no luck. The following really simple segment:

#include <iostream>
#include <complex>
int main (int argc, char * const argv[]) 
{
    std::complex<double> a(1.,1.);
    std::cout << "a = "<< a << "\n";
    return 0;
}

using Xcode 3.2 (the project setting is 'Command Line tool') on OSX 10.6.8 compiles fine and produces the following output:

a = (

when of course it should produce:

a = (1.,1.)

Yes, I can display the real and imaginary parts using a.real(), a.imag() but the above should work.

Any ideas why Xcode has this weird behaviour?

Has anyone else seen this?

Thanks in advance,

mk ii

Xcode 3.2-OTHER, Mac OS X (10.6.8)

Posted on Jan 24, 2013 3:30 PM

Reply

Answer 1

etresoft

Level 9

56,656 points

Jan 24, 2013 5:22 PM in response to mk ii

Xcode 3.2 is ancient. That version was still using the old GCC compiler. It works fine in Xcode 4.5.2.

Reply

Answer 2

mk ii Author

Level 1

0 points

Jan 25, 2013 12:51 AM in response to etresoft

It isn't the gcc compiler, the code segment works fine if compiled using g++ in the terminal, it is almost certainly a bug in Xcode.

I'm sure it works fine on Xcode 4.5.2, but at the moment I'm stuck with Snow Leopard.

Thanks for the reply nevertheless,

m

Reply

Answer 3

g_wolfman

Level 4

3,472 points

Jan 25, 2013 6:55 AM in response to mk ii

You may very well be correct. Unfortunately, Xcode 3.2 is no longer supported, so the odds of a bug-fix are pretty much zero.

Reply

Answer 4

etresoft

Level 9

56,656 points

Jan 25, 2013 7:59 AM in response to mk ii

mk ii wrote:

It isn't the gcc compiler, the code segment works fine if compiled using g++ in the terminal, it is almost certainly a bug in Xcode.

Xcode is just an IDE. It uses the GCC compiler. You might want to double-check that you are using the correct C++ template and try running your program from the terminal instead of from Xcode. There could be some iostream buffering issues that aren't working properly when you are running from inside Xcode.

Reply

Answer 5

mk ii Author

Level 1

0 points

Jan 26, 2013 2:19 AM in response to etresoft

Thanks again, think at the moment I'll just have to work with it as it is. (FWIT the template is 'Command line tool' which is the most appropriate for the job in hand). I'm guessing some problem between Xcode and its implementation of the console.

Cheers,

m

Reply

Answer 6

Jongware

Level 2

265 points

Jan 26, 2013 2:54 AM in response to mk ii

Try adding either a newline in your output string or add "std::endl" (a newline character automatically flushes), or add an implicit std::flush.

XCode adds a wrapper around the console, and it simply might not be aware that you are done writing a string. Flushing tells it you *are*. It "works" correctly in Terminal because this automatically flushes at the end of a program.

Reply

Answer 7

mk ii Author

Level 1

0 points

Jan 27, 2013 6:17 AM in response to Jongware

Cheers Jongware, already tried the "std::endl" as well as "std::flush"... \n ... afraid none work!! but like I say am resigned to just displaying each component separately. thanks, m

Reply