Skip to content

base:System.Posix.Signals is empty on Windows

From http://www.haskell.org/pipermail/libraries/2006-August/005762.html:

Neil Mitchell:``

Why is System.Posix.Signals defined in base on Windows, but entirely blank, while System.Posix.Process is defined in Unix?

If this is a dependancy issue, then shouldn't System.Posix.Internals.Signals be in the base, and then unix export System.Posix.Signals, which is just a reexport of this?

This issue is annoying because I'm trying to at least write null stubs for the functions so I can compile a program requiring unix on Windows. It doesn't help that Windows ships a version of Signals with an entirely different interface...

Simon Marlow:\

Good point. I think this is mostly historical, System.Posix.Signals is required to bootstrap GHC, which is why it was originally in base (I think at one stage we bootstrapped using only base+haskell98). It's too late to sort this out for GHC 6.6, but we'll do something about it after the release. (feel free to submit a patch if you get to it before us).

Trac metadata
Trac field Value
Version 6.6
Type Bug
TypeOfFailure OtherFailure
Priority normal
Resolution Unresolved
Component libraries/base
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system Unknown
Architecture Unknown
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information