On Sat, Dec 09, 2006 at 09:38:37PM +0000, [EMAIL PROTECTED] wrote: > What I have discovered is that þugs, invoked with no arguments, > initializes itself differently depending upon the presence or absence > of Prelude.hs in the $HOME directory. With Prelude.hs *not* present > in $HOME, I get the behavior described in the original post. When > Prelude.hs *is* present in $HOME, then an error re loading Prelude.hs > is reported, and primMinInt/primMaxInt/primMaxChar all work and the > prompt is 'Hugs.Prelude>'.
You have a file called Prelude.hs containing a module Hugs.Prelude in your current directory. When Hugs starts, it loads Hugs.Prelude, which it finds in the default path, and then attempts to load Prelude from Prelude.hs (because . is at the front of the search path). However this file contains a module Hugs.Prelude, not the Prelude it was expecting, and initialization fails. The error message when Hugs finds a file to contain the wrong module could be better, though. _______________________________________________ Hugs-Users mailing list Hugs-Users@haskell.org http://www.haskell.org/mailman/listinfo/hugs-users
