id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	os	architecture	failure	difficulty	testcase	blockedby	blocking	related
1190	base:System.Posix.Signals is empty on Windows	igloo		"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)."	bug	closed	normal	6.8.1	libraries/base	6.6	fixed		Bulat.Ziganshin@…	Unknown/Multiple	Unknown/Multiple		Unknown