
Hi, I'm not sure what the expected behaviour ought to be so this may not be a bug... Given a Haskell script with a line like import "/home/PRG_DEV/SRC/SCRIPTS/HASKELL/MAKEFILE_GENERATOR/LdfsWrapper.hs" hi, hmake, etc (version "Version: 2.02 (2001-02-08)") all report Fail: Can't find module "/home/PRG_DEV/SRC/SCRIPTS/HASKELL/MAKEFILE_GENERATOR/LdfsWrapper.hs" in . . Or in standard libraries at /usr/local/include/nhc98 Asked for by: makeMakefile.hs [Check settings of -I or -P flags?] I'd have thought it would be allowable to use unix absolute paths (certainly gcc allows absolute paths so I presume it's not some obscure security risk). (In case anyone wants to know, the full paths are there because some of these files are used in runhugs scripts, which are themselves invoked via symlinks, so it's easier to have all imports absolute.) ___cheers,_dave________________________________________________________ www.cs.bris.ac.uk/~tweed/pi.htm |tweed's law: however many computers email: tweed@cs.bris.ac.uk | you have, half your time is spent work tel: (0117) 954-5250 | waiting for compilations to finish.

import "/home/PRG_DEV/SRC/SCRIPTS/HASKELL/MAKEFILE_GENERATOR/LdfsWrapper.hs"
Fail: Can't find module "/home/PRG_DEV/SRC/SCRIPTS/HASKELL/MAKEFILE_GENERATOR/LdfsWrapper.hs" in . Or in standard libraries at /usr/local/include/nhc98 Asked for by: makeMakefile.hs
I'd have thought it would be allowable to use unix absolute paths
Sorry, using absolute paths is a Hugs-only extension to Haskell'98. Although it works OK in an interpreter, the semantics are somewhat unclear for a compiler. After all, the compiler is not interested in the *source-file* of the import - it only wants to see the .hi file. Regards, Malcolm
participants (2)
-
D. Tweed
-
Malcolm Wallace