Aleksandar Donev wrote:
> 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).
If you're seeing numbers split in the middle, (for example, 1234 printed as
12<newline>34), that's a bug and should be reported with an example.
https://premier.intel.com/ I've never seen such behavior from the Intel
compiler.
If instead you're seeing a break between numbers, well, that's proper
behavior. The implementation is free to choose any line length it likes -
many implementations assume an 80-character width and break accordingly.
Some allow you to override this by opening the file with an explicit RECL=,
but the standard doesn't specify such behavior.
I will mention that when the future "combined technology" compiler is
released, it will use the "Compaq-heritage" (or maybe I should say
"Digital-heritage"!) I/O library and thus gain some features.
Steve Lionel
Software Products Division
Intel Corporation
Nashua, NH
|