Menu
▾
▴
#277 Missing # from #-} elicits utterly opaque error
closed-wont-fix
nobody
None
5
2003-11-03
2003-10-30
Anonymous
No
Consider this in Foo.hs
module Foo where
{-# LINE 1 "Baz.hs" -}
Notice the missing #
GHC 6.3 (HEAD, 30 Oct 2003) gives the message:
Baz.hs:0: lexical error
This is extremely opaque; after all, the error is in Foo.
And it would help to know the offending token.
Simon PJ
Logged In: YES
user_id=48280
The error message might be opaque, but there's a good reason
for it: when GHC sees
{-# LINE 1 "foo.hs"
it sets the current file to "foo.hs" and the line number to
0 (one less than 1, because the *next* line in the file is
line 1). I suppose we should really wait for the closing
'#-}' before changing the file & line number, but that's
hard (there might be intervening comments).