Message304064
| Author | torsten |
|---|---|
| Recipients | benjamin.peterson, gjb1002, gvanrossum, ncoghlan, pitrou, pjenvey, serhiy.storchaka, stutzbach, torsten, vstinner |
| Date | 2017-10-10.18:05:57 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1507658757.25.0.213398074469.issue13601@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> Looking at http://pubs.opengroup.org/onlinepubs/9699919799/functions/stdin.html (which also covers stdout and stderr), it specifically says about stderr: "When opened, the standard error stream is not fully buffered;". I was of the impression that this is defined in ISO C already. Unfortunately, I only have ISO C 99 at hand, but this clearly states in section 7.19.3 (Files), enumeration item 7: > As initially opened, the standard error stream is not fully buffered; the standard input and standard output streams are fully buffered if and only if the stream can be determined not to refer to an interactive device. I am quite sure this is just as as it was in the original ANSI C standard. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-10-10 18:05:57 | torsten | set | recipients: + torsten, gvanrossum, gjb1002, ncoghlan, pitrou, vstinner, pjenvey, benjamin.peterson, stutzbach, serhiy.storchaka |
| 2017-10-10 18:05:57 | torsten | set | messageid: <1507658757.25.0.213398074469.issue13601@psf.upfronthosting.co.za> |
| 2017-10-10 18:05:57 | torsten | link | issue13601 messages |
| 2017-10-10 18:05:57 | torsten | create | |