Changes between Version 23 and Version 24 of GhcApiStatus


Ignore:
Timestamp:
Aug 28, 2008 10:21:15 PM (6 years ago)
Author:
nominolo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GhcApiStatus

    v23 v24  
    6767}}} 
    6868 
    69 To start a GHC API session you now use: 
     69GHC internally uses `handleSourceError`, but this is only to avoid bootstrapping issues.  API clients can just use the standard extensible exception handling mechanism, but should use `gcatch`, `gtry`, etc. as these work in any monad with the proper instance. 
     70 
     71To start a 'Ghc' session use: 
    7072 
    7173{{{ 
     
    109111== Interface Changes == 
    110112 
     113'''Most (all?) GHC API clients will break''', since any function that uses a Session now has a different type.  However, these changes are usually rather straightforward.  The tricky parts are what to do with error messages.  So far, messages could be intercepted by overriding `log_action`.  This was awkward, comparable to Unix calls returning that an error code and storing it in some global variable.  OTOH, the new method requires that errors are explicitly dealt with--otherwise, exceptions will propagate and quit the program. 
     114 
    111115{{{load}}} and {{{setTarget}}} work like before.  {{{checkModule}}} 
    112116has been split up into: