GHC import bug (# 231631)

Tim Barbour trb at eastpac.com.au
Sat Oct 20 20:09:42 EDT 2001


I'm sending this to the list, because I did not get much satisfaction from the
SourceForge bug-tracking tool.

I have just encountered a GHC bug similar to the one numbered 231631 on
SourceForge.

I have some further observations about it, and a small tar file (attached)
showing how to reproduce a stronger form of it.

The bug is still present in 5.02, and it does not have to involve the current
directory - any directory in the import path will do. Nor do I see any
connection to the re-compilation system, or package manager.

Here is the (gzipped) tar file:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: import-bug.tar.gz
Type: application/octet-stream
Size: 2714 bytes
Desc: not available
Url : http://www.haskell.org/pipermail/glasgow-haskell-bugs/attachments/20011021/a5d0a185/import-bug.tar.obj
-------------- next part --------------


Note that I tried to add this information to the SourceForge bug tool, but I
could not log-in to SourceForge to submit this, even though I have a SourceForge
account! In my experience with SourceForge, this is not unusual - often when I
try to use it, something does not work. Recently, I could not get CVS access to
one of my own projects for a week or two. My six Free Software projects that
were going to go to SourceForge are now more likely to stay right on my own
sever, because it is more reliable. I might use SourceForge as the main
ftp-site, but they don't provide ftp anymore...

I think SourceForge is a great idea, and I wish it to work. But I don't want it
to interfere with the development of my software, and I think GHC people should
be careful that it is actually helping GHC, not hindering it. 

Tim
-- 
"They that can give up essential liberty to obtain a little temporary
 safety deserve neither liberty nor safety." -- Benjamin Franklin


More information about the Glasgow-haskell-bugs mailing list