On Tue, Sep 13, 2005 at 10:15:39AM +0100, Simon Marlow wrote:
> On 12 September 2005 16:34, Frederik Eaton wrote:
>
> > On Mon, Sep 12, 2005 at 12:41:32PM +0100, Simon Marlow wrote:
> >> On 20 August 2005 22:38, Frederik Eaton wrote:
> >>
> >>> Hi,
> >>>
> >>> It seems like it would be nice to h
On 12 September 2005 16:34, Frederik Eaton wrote:
> On Mon, Sep 12, 2005 at 12:41:32PM +0100, Simon Marlow wrote:
>> 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 cas
On Mon, Sep 12, 2005 at 12:41:32PM +0100, Simon Marlow wrote:
> 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 ma
]; glasgow-haskell-bugs@haskell.org
> 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
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
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
