Status of Hugs? (last major release for Windows was 2003..)
subject says it all? long gone the times when Valentine's day marked Hugs releases;-) here is the situation a windows users like me sees at the moment (I had switched to ghci, but the Haskell' effort prompts me to have two implementations of Haskell+extensions again, so I'd like to update my old Nov 2003 Hugs:-): hcar nov 2005 says "A new major release of Hugs is planned within a few months" "It should also include a Windows distribution" http://haskell.org/communities/11-2005/html/report.html#sect2.2 hugs home page says latest news last major release nov 2003 interim release mar 2005 targeted at unix systems http://www.haskell.org/hugs/ hcar also refers to winhugs, which isn't mentioned on hugs home page at all (its download page refers to an older version, stating that that one doesn't work), for a pre-release. http://www-users.cs.york.ac.uk/~ndm/projects/winhugs.php i tried minhugs from there, which claims Version: 20051031, but doesn't seem to know about the hierarchical libs. the menu entry gives a blank, and the prompt gives: Hugs> :b Data.List Unknown module Data.List cheers, claus
On Sun, Feb 19, 2006 at 10:16:21PM -0000, Claus Reinke wrote:
hcar also refers to winhugs, which isn't mentioned on hugs home page at all (its download page refers to an older version, stating that that one doesn't work), for a pre-release.
Yes, please try that out. When WinHugs is ready, there will be a Hugs release.
i tried minhugs from there, which claims Version: 20051031, but doesn't seem to know about the hierarchical libs. the menu entry gives a blank, and the prompt gives:
Hugs> :b Data.List Unknown module Data.List
That's normal Hugs behaviour: you have to load a module before you can browse it.
Yes, please try that out. When WinHugs is ready, there will be a Hugs release.
It's pretty much ready now, I'll package up some final binaries tomorrow - whenever Hugs is in a ready state I'm happy to release.
the menu entry gives a blank out of curiosity, what were you hoping the menu entry to say to indicate heirarchical modules? If there is a part of the user interface I've missed out (esp that was there in previous versions of WinHugs) just let me know.
Thanks Neil
It's pretty much ready now, I'll package up some final binaries tomorrow - whenever Hugs is in a ready state I'm happy to release.
looking forward to a full release. 1. could you please add some text wrt the difference between minhugs and winhugs? what is the reason for the huge size difference/why might one prefer winhugs in spite of its size? the current page only says that the bigger download has more contents, which is as true as unhelpful;-) so I stuck with minhugs. 2. could you please coordinate with ghc HQ about non-exclusive use of file associations? minhugs asks whether to register, and ghc snapshots can be unpacked and used without registering, so that is okay. but I think when either ghc or hugs is allowed to register itself for Haskell files, it should *not override* existing associations, but *extend* them. (e.g., I like to have both hugs and ghci on the menu, but default to vim for Haskell files). 3. is minhugs a complete Hugs, or what is missing/not working? ffi? hgl? 4. minhugs is quite nice, and many of the additions seem actually useful (instead of just buttons for everything;-), with editor integration via source links, colour, copy&paste, drap&drop, help and browsing.
the menu entry gives a blank out of curiosity, what were you hoping the menu entry to say to indicate heirarchical modules? If there is a part of the user interface I've missed out (esp that was there in previous versions of WinHugs) just let me know.
there is a help menu entry for hierarchical libraries, which does nothing in minhugs. in ghci, the corresponding help entry takes me to the local copy of the haddocs for those libraries, which I use all the time. btw, which user docs do the help contents correspond to? as long as the contents have not been integrated into one document, why are not all current user docs available? Cheers, Claus
1. could you please add some text wrt the difference between minhugs and winhugs? what is the reason for the huge size difference/why might one prefer winhugs in spite of its size?
True, good point. I have added this to the web page: The things lacking from MinHugs that are in WinHugs are the console version of hugs and runhugs, and lots of libraries. In particular OpenGL and Win32 have been removed. The main WinHugs interface is the same between both, and both accept the same Haskell language and all Hugs extensions. At the moment both are missing FFI.
2. could you please coordinate with ghc HQ about non-exclusive use of file associations? will do
but I think when either ghc or hugs is allowed to register itself for Haskell files, it should *not override* existing associations, but *extend* them. (e.g., I like to have both hugs and ghci on the menu, but default to vim for Haskell files).
definately. Although note that if you use the WinHugs Edit menu entry link, and configure your editor properly via WinHugs (it may even be able to auto-config for Vim, since thats a known one) then the Edit command WinHugs inserts will actually spawn Vim automatically.
3. is minhugs a complete Hugs, or what is missing/not working? ffi? hgl? Detailed in 1, both are missing FFI currently
4. minhugs is quite nice, and many of the additions seem actually useful (instead of just buttons for everything;-), with editor integration via source links, colour, copy&paste, drap&drop, help and browsing. :)
there is a help menu entry for hierarchical libraries, which does nothing in minhugs. in ghci, the corresponding help entry takes me to the local copy of the haddocs for those libraries, which I use all the time. Woops, that link seems to have been neglected. Since Hugs doesn't install Haddock documentation it should fire up a web browser, but yeah, I'll fix that.
btw, which user docs do the help contents correspond to? as long as the contents have not been integrated into one document, why are not all current user docs available? Having two entirely separate user guides (one called user guide, one called user manual) confused me totally. I had no idea what each one was, and no idea where to go to find things. I've put a link to the newest one, if the newest one misses information then I'd say thats less confusing than having two links!
Thanks Neil
participants (3)
-
Claus Reinke -
Neil Mitchell -
Ross Paterson