diff options
author | dimitri <dimitri@afe2bf4a-e733-0410-8a33-86f594647bc7> | 2003-06-15 18:25:48 (GMT) |
---|---|---|
committer | dimitri <dimitri@afe2bf4a-e733-0410-8a33-86f594647bc7> | 2003-06-15 18:25:48 (GMT) |
commit | 25a65bed9e3548070b1af401db683bfb0cce9de0 (patch) | |
tree | 567da63962a903f646bb092a950026c75a8369d8 /doc/faq.doc | |
parent | d863498bbf7129c5d7f4984ca00adf378aac246d (diff) | |
download | Doxygen-25a65bed9e3548070b1af401db683bfb0cce9de0.zip Doxygen-25a65bed9e3548070b1af401db683bfb0cce9de0.tar.gz Doxygen-25a65bed9e3548070b1af401db683bfb0cce9de0.tar.bz2 |
Release-1.3.2
Diffstat (limited to 'doc/faq.doc')
-rw-r--r-- | doc/faq.doc | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/faq.doc b/doc/faq.doc index 74dc805..d9f3f6d 100644 --- a/doc/faq.doc +++ b/doc/faq.doc @@ -195,15 +195,15 @@ 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 grammer of X is close to C or C++, then it is probably not too hard to +- 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 for all other languages directly supported by doxygen (i.e. Java, IDL, C#, PHP). -- If the grammer of X is somewhat different than you can write an input +- 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). -- If the grammer is completely different one could write a parser for X and +- 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). @@ -218,8 +218,8 @@ where this might happen is if you have lines in your code with more than 16K characters. If you have run into such a case and want me to fix it, you -should send me a code fragment that triggers the message. The workaround -the problem put some line-breaks into your file, split it up into smaller +should send me a code fragment that triggers the message. To work around +the problem, put some line-breaks into your file, split it up into smaller parts, or exclude it from the input using EXCLUDE. <li><b>When running make in the latex dir I get "TeX capacity exceeded". Now what?</b> |