summaryrefslogtreecommitdiffstats
path: root/doc/faq.doc
diff options
context:
space:
mode:
authorDimitri van Heesch <dimitri@stack.nl>2018-09-01 09:30:50 (GMT)
committerDimitri van Heesch <dimitri@stack.nl>2018-09-01 09:30:50 (GMT)
commitbaba2724a4a76719d4bcff093d64ec50cd53db57 (patch)
treebb399b3f87186aea76c4114beea7e603ac75f62f /doc/faq.doc
parent8970cd397fdbce240878e88132c1bd7851637f13 (diff)
downloadDoxygen-baba2724a4a76719d4bcff093d64ec50cd53db57.zip
Doxygen-baba2724a4a76719d4bcff093d64ec50cd53db57.tar.gz
Doxygen-baba2724a4a76719d4bcff093d64ec50cd53db57.tar.bz2
Update mail address
Diffstat (limited to 'doc/faq.doc')
-rw-r--r--doc/faq.doc2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/faq.doc b/doc/faq.doc
index e9c93d8..f48e109 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.stack.nl/~dimitri/doxygen/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).