Where is runghc documented, by the way? I find only a mention of it in the user's guide.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Simon Marlow > Sent: Monday, September 12, 2005 7:42 AM > To: [EMAIL PROTECTED]; [email protected] > Subject: RE: runghc takes modules from current working directory > > On 20 August 2005 22:38, Frederik Eaton wrote: > > > Hi, > > > > It seems like it would be nice to have runghc not take modules from > > the current working directory in many cases since it breaks > > abstraction. It looks like it may be only a real problem for > > debugging, when modules are supposed to be in a package > somewhere, but > > aren't, and the current directory happens to have files of the same > > name, but in those cases it can be quite a pain to track down the > > error. The problem comes up especially often when one writes scripts > > in haskell to work with haskell packages or generate > haskell code. Do > > people frequently use the "find modules in the current directory" > > feature, or could they be asked to do that with > > > > {-# OPTIONS_GHC -i. #-} > > > > ? (I don't think this works yet) Otherwise maybe a special option > > could be added to tell runghc not to look in the current directory? > > > > Frederik > > runghc -i foo.hs? > > Cheers, > Simon > _______________________________________________ > Glasgow-haskell-bugs mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs > _______________________________________________ Glasgow-haskell-bugs mailing list [email protected] http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
