summaryrefslogtreecommitdiff
path: root/unittests/Option
diff options
context:
space:
mode:
authorSean Silva <silvas@purdue.edu>2012-12-05 00:26:32 +0000
committerSean Silva <silvas@purdue.edu>2012-12-05 00:26:32 +0000
commitee47edfd8e2dd048522ebd47305aeefbe9d8729c (patch)
tree1149ccaddfcba655771ab114e383a2cae3b6b200 /unittests/Option
parent4e5448053163e0d9c2107b240ccdb5a95c107b07 (diff)
downloadllvm-ee47edfd8e2dd048522ebd47305aeefbe9d8729c.tar.gz
llvm-ee47edfd8e2dd048522ebd47305aeefbe9d8729c.tar.bz2
llvm-ee47edfd8e2dd048522ebd47305aeefbe9d8729c.tar.xz
docs: Sphinxify `docs/tutorial/`
Sorry for the massive commit, but I just wanted to knock this one down and it is really straightforward. There are still a couple trivial (i.e. not related to the content) things left to fix: - Use of raw HTML links where :doc:`...` and :ref:`...` could be used instead. If you are a newbie and want to help fix this it would make for some good bite-sized patches; more experienced developers should be focusing on adding new content (to this tutorial or elsewhere, but please _do not_ waste your time on formatting when there is such dire need for documentation (see docs/SphinxQuickstartTemplate.rst to get started writing)). - Highlighting of the kaleidoscope code blocks (currently left as bare `::`). I will be working on writing a custom Pygments highlighter for this, mostly as training for maintaining the `llvm` code-block's lexer in-tree. I want to do this because I am extremely unhappy with how it just "gives up" on the slightest deviation from the expected syntax and leaves the whole code-block un-highlighted. More generally I am looking at writing some Sphinx extensions and keeping them in-tree as well, to support common use cases that currently have no good solution (like "monospace text inside a link"). git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@169343 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'unittests/Option')
0 files changed, 0 insertions, 0 deletions