[ ghc-Bugs-832920 ] Missing # from #-} elicits utterly opaque error

Bugs item #832920, was opened at 2003-10-30 09:17
Message generated for change (Comment added) made by simonmar
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108032&aid=832920&group_id=8032

Category: None
Group: None
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Missing # from #-} elicits utterly opaque error

Initial Comment:
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 

----------------------------------------------------------------------

>Comment By: Simon Marlow (simonmar)
Date: 2003-11-03 13:04

Message:
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).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108032&aid=832920&group_id=8032