#5510: Representation of GHC Errors
---------------------------------+------------------------------------------
Reporter: mgsloan1 | Owner:
Type: feature request | Status: new
Priority: normal | Milestone:
Component: GHC API | Version: 7.2.1
Keywords: | Testcase:
Blockedby: | Difficulty:
Os: Unknown/Multiple | Blocking:
Architecture: Unknown/Multiple | Failure: None/Unknown
---------------------------------+------------------------------------------
Comment(by simonpj):
Changing all GHC's errors to use a data type instead would be a major
task. There are so many of them! And they change frequently. Any change
to an error message would then involve
* Changing the data type
* Changing its pretty printer
* Recompiling every module that could generate errors (because the data
type changed)
Moreover, the text of the message would be generated in the pretty
printer, far away from the module that generated it in the first place.
When changing the latter, that makes it harder to see what error messages
will arise from a paricular event.
So I think it's laudable in principle -- it would allow clients of the GHC
API to take different action depending on what kind of error arise -- but
I think it would be quite a big deal in practice.
Maybe you can say more about your application? Maybe something less large
scale woudl suffice.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/5510#comment:1>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
