Re: g++ problem - Thanks

Thanks - I was just out of date. It works now. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: g++ problem

On 2/8/06, Thomas H. George <[EMAIL PROTECTED]> wrote: > As a occasional programmer I tried to recompile an old program I > intended to expand. Although #include was entered before the > start of main the g++ compiler did not recognize cin and cout. This > seems so elementary it certainly shoul

Re: g++ problem

On 2006-02-08T20:26:58-0500, Thomas H. George wrote: > As a occasional programmer I tried to recompile an old program I > intended to expand. Although #include was entered before the > start of main the g++ compiler did not recognize cin and cout. Add a "using namespace std;" or prefix each ci

g++ problem

As a occasional programmer I tried to recompile an old program I intended to expand. Although #include was entered before the start of main the g++ compiler did not recognize cin and cout. This seems so elementary it certainly shouldn't have changed and it certainly worked before as I am us

cin/cout g++ problem

Any idea why this code shouldn't be executing flawlessly? The program stops for the first query and input, then leaves the function without asking for or getting a reply to the second query Putting in cout.flush() and changing the second input to string, using printf, and ending with an explicit

g++ problem

Hi there, Attached is a tarball with a very short program that doesn't work on recent upgrades of woody (around here - i386), but works everywhere else, including potato. It appears to occur when linking shared object files against the C++ libs. to run : tar zxvf broken.tgz export LD_LIBRARY_PA