>> ... snip ...

>>> That was a rhetorical question. I was simplily noting that the
>>> Standard specifies for '\f' something which sounds very like "if
>>> the stream you're writing to is a terminal window or screen, clear
>>> it", but gcc does something different (but it has the right to do
>>> that, since the Standard never defines "page"), and lcc-win32 does
>>> something wrong (unless "logical page" is taken to mean "a portion
>>> of output delimited by female (Venus) symbols"...) :-)

>> No, gcc (and any legal compiler) simply arranges to output the '\f'
>> character.  What the system does with it is up to the system.

> Do you mean that if a program compiled with lcc-win32 from
>  #include <stdio.h>
>  int main(void) {
>     puts("AAAA\fAAA!");
>     return 0;
>  }
> when executed displays AAAA?AAA!, then it is a problem of Windows,
> not of lcc-win32?