[GHC] #11180: A program writing to a read-only stdout should not succeed

GHC ghc-devs at haskell.org
Tue Dec 8 23:10:46 UTC 2015


#11180: A program writing to a read-only stdout should not succeed
-------------------------------------+-------------------------------------
        Reporter:  thomie            |                Owner:
            Type:  bug               |               Status:  new
        Priority:  normal            |            Milestone:
       Component:  Compiler          |              Version:  7.10.2
      Resolution:                    |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:
                                     |  Unknown/Multiple
 Type of failure:  None/Unknown      |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by rwbarton):

 That seems needlessly spiteful and different from every other language and
 will cause many more data loss problems.

 It's traditionally the programmer's responsibility to close handles that
 they opened, but the handles `stdin`/`stdout`/`stderr` are opened
 automatically and so it makes sense to close them automatically too, or at
 least behave as though they are closed (by flushing the buffers).

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/11180#comment:4>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler


More information about the ghc-tickets mailing list