Aleksandar Donev writes:
> One more thing oddity is coming up with this compiler: list-directed IO.
> Intel seems to have a pretty funky IO library, which takes great
> liberties in putting extra spaces and line-breaks in list-directed
> output. For example, it seems to break things at the 72 column, thus
> leaving numbers split in the middle (which my post-processing cannot
> parse of course).
>
> Does anyone know of a way to change this via switches? (yes, yes, I know
> some of you don't like list-directed IO, but some of us are lazy and
> don't want to write format strings...).
I seriously doubt it. I don't recall ever yet seeing a compiler that
allowed you to control list-directed I/O behavior by compiler
switches. That's exactly why many of us don't "like" list-directed
I/O. It isn't actually a matter of "liking"; I do like its
simplicity. I use it a lot, particularly for quick hacks and
debugging. I also know that you are at the mercy of the compiler's
choices. If you don't like those choices then you need to use
explicit formats, like it or not.
The only think I'd say that I don't "like" about list-directed
formatting is the amount of time I have to spend answering variants of
the same question. There are lots of variants, but they all boil
down to the same thing, and they all have the same answer: that
if you aren't willing to put up with whatever the compiler chooses
to do (and different compilers make different choices), you have
to use an explicit format.
--
Richard Maine | Good judgment comes from experience;
[log in to unmask] | experience comes from bad judgment.
| -- Mark Twain
|