diff options
| author | albert-github <albert.tests@gmail.com> | 2018-02-26 12:19:36 (GMT) |
|---|---|---|
| committer | albert-github <albert.tests@gmail.com> | 2018-02-26 12:19:36 (GMT) |
| commit | 17c8c0ee8c0dd06938f3b85db6361de24c1bbe58 (patch) | |
| tree | 1d001306f94336cf82dc8c1b35b9a08c271260be | |
| parent | b6f01ff09b17e5c2288f2418ef0a8f074456c357 (diff) | |
| download | Doxygen-17c8c0ee8c0dd06938f3b85db6361de24c1bbe58.zip Doxygen-17c8c0ee8c0dd06938f3b85db6361de24c1bbe58.tar.gz Doxygen-17c8c0ee8c0dd06938f3b85db6361de24c1bbe58.tar.bz2 | |
Documentation corrections
Corrected the way files are displaced (should be in "code mode")
| -rw-r--r-- | doc/arch.doc | 4 | ||||
| -rw-r--r-- | doc/faq.doc | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/doc/arch.doc b/doc/arch.doc index e5fbbdc..337f4dd 100644 --- a/doc/arch.doc +++ b/doc/arch.doc @@ -139,8 +139,8 @@ strings and executes the commands it finds in it (this is the second pass in parsing the documentation). It writes the result directly to the output generators. -The parser is written in C++ and can be found in src/docparser.cpp. The -tokens that are eaten by the parser come from src/doctokenizer.l. +The parser is written in C++ and can be found in \c src/docparser.cpp. The +tokens that are eaten by the parser come from \c src/doctokenizer.l. Code fragments found in the comment blocks are passed on to the source parser. The main entry point for the documentation parser is \c validatingParseDoc() diff --git a/doc/faq.doc b/doc/faq.doc index bbad8c0..61d516b 100644 --- a/doc/faq.doc +++ b/doc/faq.doc @@ -210,7 +210,7 @@ remove the % and keep the word unlinked. No, not as such; doxygen needs to understand the structure of what it reads. If you don't mind spending some time on it, there are several options: - If the grammar of X is close to C or C++, then it is probably not too hard to - tweak src/scanner.l a bit so the language is supported. This is done + tweak \c src/scanner.l a bit so the language is supported. This is done for all other languages directly supported by doxygen (i.e. Java, IDL, C#, PHP). - If the grammar of X is somewhat different than you can write an input @@ -219,7 +219,7 @@ If you don't mind spending some time on it, there are several options: Javascript, see http://www.stack.nl/~dimitri/doxygen/download.html#helpers). - If the grammar is completely different one could write a parser for X and write a backend that produces a similar syntax tree as is done by - src/scanner.l (and also by src/tagreader.cpp while reading tag files). + \c src/scanner.l (and also by \c src/tagreader.cpp while reading tag files). \section faq_lex Help! I get the cryptic message "input buffer overflow, can't enlarge buffer because scanner uses REJECT" |