aboutsummaryrefslogtreecommitdiff
path: root/src/Haddock/Lex.x
Commit message (Collapse)AuthorAgeFilesLines
* One pass parser and tests.Mateusz Kowalczyk2014-01-121-255/+0
| | | | | | | | We remove the HTML test as it is no longer necessary. We cover the test case in spec tests and other HTML tests but keeping this around fails: this is because the new parser has different semantics there. In fact, I suspect the original behaviour was a bug that wasn't caught/fixed but simply included as-is during the testing.
* Use Alex 3's Unicode support to properly lex source files as UTF-8Max Bolingbroke2013-03-101-23/+42
| | | | Signed-off-by: David Waern <david.waern@gmail.com>
* Fix parser bugSimon Hengel2012-10-091-1/+3
|
* Simplify lexing/parsing of propertiesSimon Hengel2012-10-091-8/+2
| | | | | In contrast to what we do for examples, we do not really need to capture the "prompt" here.
* Add markup support for propertiesKazu Yamamoto2012-10-091-0/+8
|
* Don't crash on unicode strings in doc comments.David Waern2012-04-011-1/+2
|
* Give preference to type over data constructors for doc comment links at ↵David Waern2011-11-261-5/+5
| | | | | | | | | | | renaming time. Previously this was done in the backends. Also, warn when a doc comment refers to something that is in scope but which we don't have the .haddock file for. These changes mean we can make DocIdentifier [a] into DocIdentifier a.
* Remove #ifs for older compiler versions.David Waern2011-11-251-4/+0
|
* Hack this to make it work with both Alex 2.x and Alex 3.x. Unicode inSimon Marlow2011-10-041-2/+32
| | | | | | | documentation strings is (still) mangled. I don't think it's possible to make it so that we get the current behaviour with Alex 2.x but magic Unicode support if you use Alex 3.x. At some point we have to decide that Alex 3.x is a requirement, then we can do Unicode.
* Fix buildIan Lynagh2011-06-171-5/+12
|
* Solve conflictsDavid Waern2010-12-071-0/+1
|
* Alex generates BangPatterns, so make Lex.x accept themsimonpj2010-11-151-1/+0
| | | | (It'd be better for Alex to generate this pragma.)
* Add BangPatterns to alex and happy source filesDavid Waern2010-11-211-0/+1
|
* Remove code for ghc < 7David Waern2010-11-151-4/+0
|
* follow changes in the GHC APISimon Marlow2010-10-271-0/+4
|
* Replace ghci> with >>> in example syntaxDavid Waern2010-09-011-3/+3
|
* WibbleDavid Waern2010-09-011-1/+1
|
* support both kinds of enumerated lists in doc markupMark Lentczner2010-08-261-0/+1
| | | | | | | | The documentation for Haddock says enumerated lists can use either of (1) first item 2. second item The second form wasn't actually supported
* Fix build with ghc < 6.13David Waern2010-07-241-0/+4
|
* Follow mkPState argument order changeIan Lynagh2010-07-061-1/+1
|
* Fix #112David Waern2010-04-101-14/+14
| | | | | | | | No link was generated for 'Addr#' in a doc comment. The reason was simply that the identifier didn't parse. We were using parseIdentifier from the GHC API, with a parser state built from 'defaultDynFlags'. If we pass the dynflags of the module instead, the right options are turned on on while parsing the identifer (in this case -XMagicHash), and the parse succeeds.
* Let parsing fails on paragraphs that are immediately followed by ansimon.hengel2010-04-081-0/+1
| | | | | | example This is more consistent with the way we treat code blocks.
* Fix #118David Waern2010-04-081-3/+3
| | | | | Avoid being too greedy when lexing URL markup (<..>), in order to allow multiple URLs on the same line. Do the same thing with <<..>> and #..#.
* Fix #75David Waern2010-04-071-1/+1
| | | | Add colons to the $ident character set.
* Propagate source positions from Lex.x to Parse.yDavid Waern2010-04-071-19/+24
|
* Add markup support for interactive examplessimon.hengel2010-04-021-0/+14
|
* Move H.Interface.Parse/Lex to H.Parse/LexDavid Waern2009-11-281-0/+172
These are not just used to build Interfaces.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-11 07:56:15 +0000