Hi, I've been working on rewriting WinHugs recently, to make it work and to make it more Windows compliant. I have put a screenshot up at http://www-users.cs.york.ac.uk/~ndm/projects/winhugs.php, and my todo list is http://www.haskell.org/hawiki/NeilMitchell/HugsNotes which includes the bugs I'm working on, and a list of the good and bad points about the rewrite. I have a version which I am now using as my primary development environment. Its stable and reliable. Out of the bugs mentioned in the Todo list only the options dialog not giving people -/+98 and other super-haskell options is real enough to stop people using it, if they want non-standard haskell. All the others are very minor. While I'm rewriting it I've tried to reduce the amount Hugs knows about WinHugs. For example, I've removed #include <windows.h> from prelude.h. There are quite a few changes to the hugs files, 8 files have been modified, none that substantially. All the changes are pretty local, and in general seem to be positive ones, I think. The changes in the WinHugs directory are pretty much total, its almost unrecognisable. There are 4 chunks of code that have survived, and those have all been marked with big warnings. Most of the files have changed name, there are a lot more smaller and self contained modules. It's not the same at all. Once the first modifications are made to the hugs directory, the existing winhugs code will be dead forever, the two code bases are sufficiently different that its unlikely to be able to run them side by side off the same hugs code, without some effort (not too much, but I can't imagine anyone will want to do it). With this in mind, how would be best to go about merging in WinHugs2? 1) Delete WinHugs and start from scratch. 2) Make a WinHugs2 directory, and keep WinHugs around for the past, accepting it probably won't build. 3) Find someone who wants to resurect the dead WinHugs1... (maybe) And also when does WinHugs2 integration want to take place? Thanks Neil