Changes between Version 7 and Version 8 of GhcApiStatus


Ignore:
Timestamp:
May 15, 2008 2:18:15 PM (7 years ago)
Author:
nominolo
Comment:

Start describing use case and non-functional requirements

Legend:

Unmodified
Added
Removed
Modified
  • GhcApiStatus

    v7 v8  
    55Simon Marlow reported that the last time he tried to work on the GHC API, it turned into a huge refactoring task.  This could mean that it may take a while until bigger changes are visible and it is very likely that programs that currently use the GHC API will break.  Hopefully, though, it will lead to a more usable GHC API and maybe to a more hackable code base in general. 
    66
    7 I plan to work with a use case and try to make it as clear and simple as possible by adapting the GHC API.
     7I plan to work with a use case and try to make it as clear and simple as possible by adapting the GHC API.  The use case will be a program that generates HTML pages for Haskell programs which will give access to more and more semantic information.  E.g. it will start out with linking references of names to their definitions (possibly to import statement or link to other module), then give typing information, and later give types for sub-expressions.  A lot of this is already possible, but some may not. 
     8
     9This use case will hopefully reflect many features an IDE or code analysis tools need.  Once this is working, we can move on to performing various transformations on the given code, or only a selected part of it.  This will should help figure out what information needs to be available to work with exposed, separate compilation phases.
     10
     11There are also a few non-functional requirements:
     12
     13 * Using the API should be fairly self-explainatory and safe.  I.e., where necessary inputs are checked for invariants and there should be no implicit dependencies.  More concretely:
     14   * If several phases use the same AST, the AST will contain a type parameter which corresponds to the phases that have been performed with it.  Hence, if a function requires input of type {{{AST Phase3}}} then it is clear that the phases with types {{{AST Phase2 -> AST Phase3}}} and {{{AST Phase1 -> AST Phase3}}} must be performed first.
     15   * GHC uses some evil hacks to simulate global variables but has some implicit assumptions when those are actually accessible.  If you call a function too early, ie., before a certain variable is initialised, GHC will die with a very unhelpful error message.  I hope to make as many of those dependencies explicit and encode those dependencies via the API (mostly via types).
     16   
    817
    918== Trac Tickets Related to the GHC API ==
     
    1221 * #1886 - GHC API should preserve and provide access to comments
    1322 * #654 - Cabalization of the GHC library.
    14  * #1631 - Make the External Package Table contain {{{ModDetails}}} not {{{ModIface}}}
    1523
    1624=== Possibly Related ===
    1725
    1826 * #2159 - Use a more efficient representation than {{{[DynFlag]}}}
     27 * #1631 - Make the External Package Table contain {{{ModDetails}}} not {{{ModIface}}}
    1928
    2029== Related Documents and Discussions ==
     
    5665   such as {{{unsafeCast#}}}, or whatever it was). that might require
    5766   a standard for typeReps, if I recall correctly.. (Claus Reinke)
     67 * ... more comments here ...
     68