Re: [Doxygen-users] BUG: Input FILE_PATTERNS fails with "c*.h" and "c*.cpp"

[Roland T. <rol...@li...>]

 >Is what you are saying that setting FILE_PATTERNS to c*.cpp c*.h will
 >include all files even those not starting with a "c"? I haven't been able
 >to reproduce that, with a simple set of empty files.
 >...

Here is a zip with a few files. Command 'doxygen A_L.cfg'  fails : doxygen 
parses p* and r* files which are NOT in the wildcards of FILE_PATTERNS. 
This fails with:
Win2k SP2 and doxygen 1.2.12
Win Me and doxygen 1.2.9.1
Win 98 SP2 and doxygen 1.2.9.1

	If I delete the line with 'c', it works fine.( only a* to l* files, but no 
c*).

 >...
 >By the way: you can also specify ranges like [a-l]*.cpp
 >...
Putting [a-l]*.h [a-l]*.cpp in FILE_PATTERNS doesn't work. In my sample, 
only a* and d* files are parsed.  (WinMe, dowygen 1.1.9.1).

Thinking that my cfg files were bad, I asked doxygen to make a brand new 
config file, and set
INPUT                  = .
FILE_PATTERNS          = [a-l]*.h [a-l]*.cpp
Same result: only a* and d* files are parsed (again WinMe, dowygen 
1.1.9.1).. Perhaps long names are not well parsed ? Or more probably I am 
missing something big ??

I was aware that one can use wildcards. But I don't know if widcards are 
sytem dependant, or are parsed as regular expressions by doxygen itself. A 
few words about wildcard would be nice in the doc.

But I am now thinking that the way I tried for cutting down processing time 
is not the right one. In fact, index.html files generated for each of the 
config files are written at the same place (will not work). Even I specify 
output directories to doxygen, final result will not be exactly the same as 
single config file (i.e. no-tagfile) doc.

I would like to get a full documentation, as one generated by a single 
config file doxygen process. But tag files (as I understand them) only 
provide links between documentations, each one having a mainpage, an index 
and so on. Is there a way to do this ?


Thank for the great tool !
Regards