tor 2002-04-25 klockan 01.07 skrev Johan Nordlander:
> One might also argue that the problem is these extra roots that
> are implicitly added to the search path. Arguably, dropping the
> current directory and the directory of the importing module from
> the search path would solve the problems
On Thursday, April 25, 2002, at 09:20 , Martin Norbäck wrote:
> tor 2002-04-25 klockan 01.07 skrev Johan Nordlander:
>> One might also argue that the problem is these extra roots that
>> are implicitly added to the search path. Arguably, dropping the
>> current directory and the directory of the
On Thursday, April 25, 2002, at 03:00 , Alastair Reid wrote:
>> Now, since there's nothing that prevents the directory hierarchies
>> starting at these roots from overlapping, we have a potential for
>> ambiguity when we want to map module names to filenames.
>
> This suggests that we might want
> All in all, dropping all implicit directories from the search
> path gets my vote.
"me too".
I wasn't aware that Hugs did this, and GHCi certainly doesn't. It's
reasonable to leave "." in the default search path, but adding an
implicit root for an imported module will certainly lead to tro
On Thursday, April 25, 2002, at 11:30 , Simon Marlow wrote:
>> All in all, dropping all implicit directories from the search
>> path gets my vote.
>
> "me too".
>
> I wasn't aware that Hugs did this, and GHCi certainly doesn't. It's
> reasonable to leave "." in the default search path, but addin
Hi, I have to hand in my final project for my degree next week. I've been
running my program through hugs most of the time, and I wanted to compile
it to an executable, so I used ghc. Unfortunately ghc makes the program
behave in a different, undesirable way. The code where the problem lies
NOTE: Even the examples are correct in the H98 libraries documentation in the
IO module section, they are incorrect in the H98 Report:
http://www.haskell.org/onlinereport/io-13.html
Scroll down, to 7.2.
> when I put the same code through ghc, it waits for a command first, and
> then when the
> On Thursday, April 25, 2002, at 11:30 , Simon Marlow wrote:
>
> >> All in all, dropping all implicit directories from the search
> >> path gets my vote.
> >
> > "me too".
> >
> > I wasn't aware that Hugs did this, and GHCi certainly doesn't. It's
> > reasonable to leave "." in the default sear
Thanks very much everyone!
I added the line "hFlush stdout" to the code and it works fine now - thanks for your
help!
Rich.
___
Glasgow-haskell-users mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
> > >> All in all, dropping all implicit directories from the search
> > >> path gets my vote.
> > >
> > > "me too".
I vote for this provided "." isn't implicitly in the search path either.
Or, rather, I vote for that assuming that my proposal [see below] isn't
going to be accepted, which I'm pr
>> This suggests that we might want to modify the search algorithm to
>> find all matches and report and error if two or more candidate
>> files are found. If this is a big performance hit, we could make
>> it a :set option.
> But wouldn't that just prohibit the use of module names that also
>
Johan:
> A reasonable compromise, although it wouldn't address the last two
> examples of module confusion that Alastair reported.
Just to clarify: my problem was that I couldn't find any way of making
Hal's example work. If there's been anything which worked, I'd have
said it was a bug in the
> On Thursday, April 25, 2002, at 03:00 , Alastair Reid wrote:
>
> >> Now, since there's nothing that prevents the directory hierarchies
> >> starting at these roots from overlapping, we have a potential for
> >> ambiguity when we want to map module names to filenames.
> >
> > This suggests that
On Thursday, April 25, 2002, at 07:05 , Simon Marlow wrote:
>> On Thursday, April 25, 2002, at 03:00 , Alastair Reid wrote:
>>
Now, since there's nothing that prevents the directory hierarchies
starting at these roots from overlapping, we have a potential for
ambiguity when we wan
14 matches
Mail list logo
