DJ Delorie <[EMAIL PROTECTED]> writes: >> That script doesn't really parse the file at all, it just scans for >> #include lines, and it processes each header only once no matter how >> many files reference it. Which has got to be faster than what >> cpplib is doing. > > Right, I figured you could run it once just to see how *much* faster > it is (if at all), so you know (perhaps) how much faster you could > make cpplib run. If it's 3x faster, that's a good reason to try to > optimize cpplib. If it's only 5% faster, maybe your time is better > spent elsewhere.
Oh! I feel decidedly unclever now. It is from 2x to 7x faster, depending on whether the filesystem cache is primed. There doesn't seem to be any way to get it to read multiple include directories, so the results are not entirely accurate, but that's a fixable problem. zw
