Title: RE: Strange cout behaviour

It doesn't matter __FILE__ : when I change it to "Hello, World" it doesn't print on speedy machine and print on slow machine! Something with time slice?

g++ -E say in both cases the same:
./aaa: line 37: namespace: command not found
./aaa: line 39: syntax error near unexpected token `newline'
./aaa: line 39: `  template<class _CharT>'


> -----Original Message-----
> From: Shlomi Fish [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 08, 2003 6:24 PM
> To: '[EMAIL PROTECTED]'
> Cc: Boulgakov Andrei
> Subject: Re: Strange cout behaviour
>
>
> On 8 Jan 2003, Oleg Goldshmidt wrote:
>
> > Boulgakov Andrei <[EMAIL PROTECTED]> writes:
> >
> > > Hi!
> > > I compile and run small application on 2  RH8 gcc3.2
> stations and get
> > > different behavior of cout:
> > > On Celeron 1000 Mhz I don't get out line without endl at
> the end(#6, output is
> > > 5 only),
> > > On PII(I?) 650 Mhz I get all lines(output 5\nfilename).
> > > What can be the cause? 
> > >
> > > 1. #include <iostream>
> > > 2. using namespace std;
> > > 3. int main()
> > > 4. {
> > > 5.        cout << __LINE__ << endl;
> > > 6.        cout << __FILE__;
> > > 7.        return 0;
> > > 8. }
> > >
> > > Boulgakov Andrei
> >
> > What's your prompt? Shell? Some shells (notably ksh) will overwrite
> > your filename with the prompt. Bash normally doesn't.
> >
>
> It may on some Mandrake configurations. zsh as well does that.
>
> Regards,
>
>       Shlomi Fish
>
> > --
> > Oleg Goldshmidt | [EMAIL PROTECTED]
> >
> > ================================To unsubscribe, send mail
> to [EMAIL PROTECTED] with
> > the word "unsubscribe" in the message body, e.g., run the command
> > echo unsubscribe | mail [EMAIL PROTECTED]
> >
>
>
>
> ----------------------------------------------------------------------
> Shlomi Fish        [EMAIL PROTECTED]
> Home Page:         http://t2.technion.ac.il/~shlomif/
> Home E-mail:       [EMAIL PROTECTED]
>
> "Let's suppose you have a table with 2^n cups..."
> "Wait a second - is n a natural number?"
>

Reply via email to