Error messages from runhugs
The error messages from runhugs seem to have gotten much worse in the version in the repository. Using old runhugs, we get: /usr/bin/runhugs -98 +o ADL3 test runhugs: Error occurred Reading file "ADL3.lhs": Reading file "/usr/share/hugs98/lib/System.hs": Reading file "Parsec": ERROR Parsec - Unable to open file "Parsec" Ooops, I guess I should put Parsec on my path. Using the version in the CVS repository, we get: $HOME/local/bin/runhugs -98 +o ADL3 test runhugs: Unable to initialise Hugs Gee, I'm not sure what I did wrong. Any chance the informative error messages can be restored? It's possible that you want to suppress the error message sometimes - so that people don't get Haskell-related error messages when using my super-duper Haskell version of cat or ls. That's cool - but there has to be a way to print the error message so that I can debug it. I am completely baffled by the above error message and have tried adding random things to my path, adding and removing .lhs from the filename, etc. - all to no avail. -- Alastair Reid reid@cs.utah.edu http://www.cs.utah.edu/~reid/
Fixed now, I believe - the handling of this part. error condition
is same as it ever was (poor), but at least the CVS contents
now avoids running into it.
hth
--sigbjorn
----- Original Message -----
From: "Alastair David Reid"
The error messages from runhugs seem to have gotten much worse in the version in the repository.
Using old runhugs, we get:
/usr/bin/runhugs -98 +o ADL3 test runhugs: Error occurred Reading file "ADL3.lhs": Reading file "/usr/share/hugs98/lib/System.hs": Reading file "Parsec": ERROR Parsec - Unable to open file "Parsec"
Ooops, I guess I should put Parsec on my path.
Using the version in the CVS repository, we get:
$HOME/local/bin/runhugs -98 +o ADL3 test runhugs: Unable to initialise Hugs
Gee, I'm not sure what I did wrong.
Any chance the informative error messages can be restored?
It's possible that you want to suppress the error message sometimes - so that people don't get Haskell-related error messages when using my super-duper Haskell version of cat or ls.
That's cool - but there has to be a way to print the error message so that I can debug it. I am completely baffled by the above error message and have tried adding random things to my path, adding and removing .lhs from the filename, etc. - all to no avail.
-- Alastair Reid reid@cs.utah.edu http://www.cs.utah.edu/~reid/
participants (2)
-
Alastair David Reid -
Sigbjorn Finne