aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Misc fixes and interface load/savedavve2006-08-133-172/+423
|
* Perfect rendering of Test.hsdavve2006-08-124-30/+57
|
* Render H98 Data declarationsdavve2006-08-123-225/+169
|
* Cleanupdavve2006-08-119-1183/+74
|
* More progressdavve2006-08-105-18/+768
|
* More Html rendering progressdavve2006-08-097-625/+654
|
* Start porting the Html rendererdavve2006-07-3012-509/+352
|
* Complete the renamerdavve2006-07-293-162/+252
|
* Add instances, build renaming environment, start on the renamerdavve2006-07-297-955/+384
|
* More work, started working on the renaming phase -- this code will need a ↵davve2006-07-232-54/+26
| | | | cleanup soon :)
* More work on pass1 -- mostly donedavve2006-07-233-78/+135
|
* More progress -- still on phase1davve2006-07-207-1512/+16
|
* More progress on the porting -- first pass starting to shape updavve2006-07-112-33/+135
|
* Progress on the porting process davve2006-07-113-21/+52
|
* Make the repos temporarily compile and illustrate a problemdavve2006-07-112-5/+5
|
* More porting work -- doesn't compiledavve2006-07-114-90/+191
|
* Initial modifications -- doesn't compiledavve2006-07-1025-2052/+375
|
* add a bug reportSimon Marlow2006-05-241-0/+3
|
* add a bugSimon Marlow2006-05-241-0/+4
|
* replace a fatal error in lexChar with a parseErrorSimon Marlow2006-05-241-2/+4
|
* add section about derivingSimon Marlow2006-05-081-0/+32
|
* record an ideaSimon Marlow2006-04-261-0/+4
|
* extend 'deriving' heuristic a littleRoss Paterson2006-04-241-6/+8
| | | | | | If an argument of a data constructor has a type variable head, it is irreducible and the same type class can be copied into the constraint. (Formerly we just did this for type variable arguments.)
* Avoid pattern guardssven.panne2006-04-202-12/+11
| | | | | | | | Due to the use of pattern guards in Haddock, GHC was called with -fglasgow-exts. This in turn enables bang patterns, too, which broke the Haddock build. Removing some unnecessary pattern guards seemed to be the better way of fixing this instead of using a pragma to disable pattern guards.
* Fixed Cabal/RPM buildSven Panne2006-03-194-15/+56
|
* bug fixes from Brad BowmanSimon Marlow2006-03-131-64/+68
|
* add PatternGuards extensionSimon Marlow2006-03-101-1/+1
|
* fixed libdir (/html was missing)benjamin.franksen2006-03-031-2/+3
|
* add haskell.vimSimon Marlow2006-03-081-0/+64
| | | | Contributed by Brad Bowman <bsb@bereft.net>, thanks!
* Add Hoogle output optionNeil Mitchell2006-02-262-0/+187
|
* add scabal-version fieldSimon Marlow2006-01-311-0/+1
|
* add a test I had lying aroundSimon Marlow2006-01-241-0/+8
|
* remove a couple TODO items that have been doneDuncan Coutts2006-01-231-5/+0
| | | | | | | | The --wiki, or rather the --comment-* options are now documented. There is probably no need to have haddock invoke unlit or cpp itself since it can now pick up the line pragmas to get the source locations right. Tools like Cabal will arrange for preprocessors to be run so there is less of a need for tools like haddock to do it themselves.
* fix markupSimon Marlow2006-01-231-2/+2
|
* Add documentation for the new --source-* and --comments-* command line optionsDuncan Coutts2006-01-231-16/+118
|
* Make the --help output fit in 80 columns.Duncan Coutts2006-01-231-15/+16
| | | | | | This is a purely cosmetic patch, feel free to ignore it. The only trickery going on is that we don't display the deprecated -s, --source flags in the help message, but we do still accept them.
* Remove the complex substitutions and add more command line flags instead.Duncan Coutts2006-01-232-61/+68
| | | | | | | | | | | | | | | | | | | Instead of incomprehensable URL substitutions like ${MODULE/./-|?m=%} we now use three seperate command line flags for the top level, per-module and per-entity source and wiki links. They are: --source-base, --source-module, --source-entity --comments-base, --comments-module, --comments-entity We leave -s, --source as an alias for --source-module which is how that option behaved previously. The long forms of the substitutions are still available, ${FILE} ${MODULE} etc and the only non-trivial substitution is ${MODULE/./c} to replace the '.' characters in the module name with any other character c. eg ${MODULE/./-} Seperating the source and wiki url flags has the added bonus that they can be turned on or off individually. So users can have per-module links for example without having to also have per-entity links.`
* Extend URL variable expansion syntax and add source links to the contents pageDuncan Coutts2006-01-223-50/+89
| | | | | | | | | | | | | | | | | | | | | | | | | Like the wiki link on the contents and index page, add a source code link too. Extend the wiki & source URL variable expansion syntax. The original syntax was: %F for the source file name (the .hs version only, not the .lhs or .hs.pp one) %M for the module name (with '.' replaced by '/') The new syntax is: %F or %{FILE} for the original source file name %M or %{MODULE} for the module name (no replacements) %N or %{NAME} for the function/type export name %K or %{KIND} for a type/value flag "t" or "v" with these extensions: %{MODULE/./c} to replace the '.' module seperator with any other char c %{VAR|some text with the % char in it} which means if the VAR is not in use in this URL context then "" else replace the given text with the '%' char replaced by the string value of the VAR. This extension allows us to construct URLs wit optional parts, since the module/file name is not available for the URL in the contents/index pages and the value/type name is not available for the URL at the top level of each module.
* Teach haddock about line pragmas and add accurate source code linksDuncan Coutts2006-01-219-177/+238
| | | | | | | | | | | | | | | | | | | | | Teach haddock about C and Haskell style line pragmas. Extend the lexer/parser's source location tracking to include the file name as well as line/column. This way each AST item that is tagged with a SrcLoc gets the original file name too. Use this original file name to add source links to each exported item, in the same visual style as the wiki links. Note that the per-export source links are to the defining module rather than whichever module haddock pretends it is exported from. This is what we want for source code links. The source code link URL can also contain the name of the export so one could implement jumping to the actual location of the function in the file if it were linked to an html version of the source rather than just plain text. The name can be selected with the %N wild card. So for linking to the raw source code one might use: --source=http://darcs/haskell.org/foo/%F Or for linking to html syntax highlighted code: --source=http://darcs/haskell.org/foo/%M.html#%N
* Rewrite pathJoin to only add a path separator when necessary.Duncan Coutts2006-01-191-4/+7
| | | | | | When the path ends in a file seperator there is no need to add another. Now using "--wiki=http://blah.com/foo/" should do the right thing. (Code snippet adapted from Isaac's FilePath package.)
* Add an optional wiki link for each top level exported name.Duncan Coutts2006-01-193-75/+130
| | | | | | | | | | | | | | In each module, for each "top level" exported entity we add a hyper link to a corresponding wiki page. The link url gets the name of the exported entity as a '#'-style anchor, so if there is an anchor in the page with that name then the users browser should jump directly to it. By "top level" we mean functions, classes, class members and data types (data, type, newtype), but not data constructors, class instances or data type class membership. The link is added at the right of the page and in a small font. Hopefully this is the right balance of visibility/distraction. We also include a link to the wiki base url in the contents and index pages.
* TODO: documnet --wikiSimon Marlow2006-01-181-0/+5
|
* Add a --wiki=URL flag to add a per-module link to a correspondng wiki page.Duncan Coutts2006-01-172-14/+40
| | | | | | | | So each html page gets an extra link (placed next to the source code and contents links) to a corresponding wiki page. The idea is to let readers contribute their own notes, examples etc to the documentation. Also slightly tidy up the code for the --source option.
* Add configure script and Makefile for the docssimonmar2005-10-297-3/+394
| | | | | | | | | Add a separate configure script and build system for building the documentation. The configure and Makefile code is stolen from fptools. This is left as a separate build system so that the main Cabal setup doesn't require a Unix build environment or DocBook XML tools.
* First cut of Cabal build systemsimonmar2005-10-1413-242/+63
|
* Start CHANGES for 0.8simonmar2005-10-141-0/+4
|
* [haddock @ 2005-10-10 15:02:55 by simonmar]simonmar2005-10-101-2/+2
| | | | | | extractRecSel: ignore non-record constructors (fixes a crash when using datatypes with a mixture of record and non-record style constructors).
* [haddock @ 2005-10-05 12:52:03 by simonmar]simonmar2005-10-051-1/+19
| | | | Document new behaviour of -s option
* [haddock @ 2005-10-05 10:51:45 by simonmar]simonmar2005-10-051-0/+3
| | | | Add a bug
* [haddock @ 2005-08-05 07:01:12 by panne]panne2005-08-051-52/+43
| | | | | | | | | | | | | Reverted to previous version (but with bumped version number), the last commit broke RPM building on SuSE systems due to differently named dependencies. As a clarification: All .spec files in the repository have to work at least on SuSE, because that's the system I'm using. And as "Mr. Building Police", I reserve me the right to keep them that way... >:-) It might very well be the case that we need different .spec files for different platforms, so packagers which are unhappy with the current .spec files should contact me, stating the actual problems.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-24 21:18:25 +0000