#946: Complete and integrate a tags and module-graph analyser using the GHC API
----------------------+-----------------------------------------------------
Reporter: simonpj | Owner: simonmar
Type: task | Status: closed
Priority: normal | Milestone: 6.8 branch
Component: Compiler | Version: 6.6
Severity: normal | Resolution: fixed
Keywords: | Difficulty: Moderate (1 day)
Testcase: N/A | Architecture: Unknown
Os: Unknown |
----------------------+-----------------------------------------------------
Changes (by guest):
* cc: [EMAIL PROTECTED] (added)
Comment:
why is this ticket closed if the tags generator isn't completed yet?
i was kind of hoping that this would be the unifying ticket for all tag
generator issues (such as #1184 and #1508), ultimately leading to a single
solution including the best of all approaches. or perhaps #1508 is meant
to be that ticket?
but even if this ticket only covers ghc api based tag generators, i'm
missing some discussion:
- simon's ticket description explicitly suggests ghc --tags rather than a
standalone tool, if this is going to be part of the ghc repo (which it
probably should)
- what is the relation between the new `utils/GhcTags.hs` and the
existing `compiler/ghci/GhciTags.hs`?
* dropping the backend processing and making it independent of ghci, i
would hope the new tool to be faster and independent of ghci limitations,
able to process more sources while providing the same level of detail in
tag files?
* :[ce]tags lets the ghc frontend do all the heavy lifting, which leads
to very detailed tag files without duplication of frontend code (and thus
no need to keep updating the name extraction code twice all the time); why
does the new tool try to do all the name extraction itself?
- what is the relation between the new tool and the old `hasktags` and
`hstags` (is the latter really still in use?)?
* i would hope the new tool to be in the same ballpark, as far as speed
is concerned, and much more detailed?
* is the need for syntactically correct sources a disadvantage in
practice, or can `ghctags` (or better: `ghc --tags`) replace `hasktags`
entirely?
perhaps the authors could comment?-)
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/946#comment:7>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
