Disclaimer - I'm not now programming in C or C++ these days, so take my comments with a pich of salt.
Jantje wrote: >Could that be due to optimisation of the code? I know that the code optimiser >sometimes does strange things and there are remarks to that end in the >compiler documentation. Indeed. I remember that Clarion has builtin runtime (not Compile-optimisation) optimisation to do cleanup, re-orgs, buffer managents, etc, in the background when your PC is idle. Frustrating when you look away to check papers and then continue working with the program just when the background processes kick in. >I have taken the habit of always use fflush if I need to be sure the buffer >has to be flushed at any given point in the program. It makes things explicit. It should work for Paul Gilmartin. But I find it still *strange* that output from ONE loop is arranged by type of output medium, not by execution sequence. But I believe from my fading memory that stderr are shown usually before stdout due to priority, but I could be wrong. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
