Hello, If there's a file called Prelude.hs in a directory, and ghci is started from that directory, ghci dies. -- Prelude.hs module A.Prelude where $ ghci GHCi, version 6.10.4: http://www.haskell.org/ghc/ :? for help Loading package ghc-prim ... linking ... done. Loading package integer ... linking ... done. Loading package base ... linking ... done. <command line>: module `Prelude' is not loaded Is there a way around this? I often like to have a modified Prelude file in a subdirectory of my project, and this behavior keeps me from being able to start ghci there. Thanks! Sean
Excerpts from Sean McLaughlin's message of Mon Nov 16 15:27:55 -0500 2009:
Is there a way around this? I often like to have a modified Prelude file in a subdirectory of my project, and this behavior keeps me from being able to start ghci there.
http://www.haskell.org/haskellwiki/No_import_of_Prelude Cheers, Edward
Hi. I'm aware of this option, and use it frequently to override the
default prelude, but it doesn't help this problem:
$ ghci -XNoImplicitPrelude
GHCi, version 6.10.4: http://www.haskell.org/ghc/ :? for help
Loading package ghc-prim ... linking ... done.
Loading package integer ... linking ... done.
Loading package base ... linking ... done.
<command line>: module `Prelude' is not loaded
On Mon, Nov 16, 2009 at 3:46 PM, Edward Z. Yang
Excerpts from Sean McLaughlin's message of Mon Nov 16 15:27:55 -0500 2009:
Is there a way around this? I often like to have a modified Prelude file in a subdirectory of my project, and this behavior keeps me from being able to start ghci there.
http://www.haskell.org/haskellwiki/No_import_of_Prelude
Cheers, Edward
Excerpts from Sean McLaughlin's message of Mon Nov 16 19:06:06 -0500 2009:
Hi. I'm aware of this option, and use it frequently to override the default prelude, but it doesn't help this problem:
I suppose this is the appropriate quote from the GHC manual: """ GHC normally imports Prelude.hi files for you. If you'd rather it didn't, then give it a -XNoImplicitPrelude option. The idea is that you can then import a Prelude of your own. (But don't call it Prelude; the Haskell module namespace is flat, and you must not conflict with any Prelude module.)""" Cheers, Edward
participants (2)
-
Edward Z. Yang -
Sean McLaughlin