diff options
author | Josh Soref <jsoref@users.noreply.github.com> | 2019-11-12 05:52:03 (GMT) |
---|---|---|
committer | Josh Soref <jsoref@users.noreply.github.com> | 2019-11-12 05:52:03 (GMT) |
commit | da08bf2be9c3470e1cf931cff3bd59c577543436 (patch) | |
tree | abb81af06f92742c2da080305c36acf5f0688050 /doc/faq.doc | |
parent | 8598cc1347fcdb05b08b1347b86490aee6b11275 (diff) | |
download | Doxygen-da08bf2be9c3470e1cf931cff3bd59c577543436.zip Doxygen-da08bf2be9c3470e1cf931cff3bd59c577543436.tar.gz Doxygen-da08bf2be9c3470e1cf931cff3bd59c577543436.tar.bz2 |
spelling: javascript
Diffstat (limited to 'doc/faq.doc')
-rw-r--r-- | doc/faq.doc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/faq.doc b/doc/faq.doc index 0ba9450..8a3aee8 100644 --- a/doc/faq.doc +++ b/doc/faq.doc @@ -216,7 +216,7 @@ If you don't mind spending some time on it, there are several options: - If the grammar of X is somewhat different than you can write an input filter that translates X into something similar enough to C/C++ for doxygen to understand (this approach is taken for VB, Object Pascal, and - Javascript, see http://www.doxygen.org/download.html#helpers). + JavaScript, see http://www.doxygen.org/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 \c src/scanner.l (and also by \c src/tagreader.cpp while reading tag files). |