help-gplusplus
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The g++ preprocessor: Include Guards


From: gutmant
Subject: Re: The g++ preprocessor: Include Guards
Date: Thu, 21 Jun 2007 13:04:58 -0000
User-agent: G2/1.0

On Jun 21, 3:31 pm, Bernd Strieder <strie...@informatik.uni-kl.de>
wrote:
> Hello,
>
>  gutm...@gmail.com wrote:
> > On Jun 21, 10:40 am, Bernd Strieder <strie...@informatik.uni-kl.de>
> > wrote:
>
> >> What I would like is a tool to find header files included
> >> unnecessarily, or those with the majority of no use where included.
> >> But this requires parsing, since it has to do even more than a
> >> compiler. The inclusion tree itself is not of too much interest for
> >> me, it's just a consequence of the necessary #includes.
>
> >> Bernd Strieder
>
> > And of the unnecessary, if you remove the optimization.
>
> Do I understand that correctly? You need that complete inclusion tree to
> e.g. allow the programmer to optimize the includes manually, so
> basically the optimization is not needed anymore, after that.
No. I need the complete inclusion tree to correct inclusion paths.
It's a little complicated.

>
> > Parsing is not a problem, we've been give python for that ;)
>
> So you think parsing or preprocessing C or even C++ is simple, then good
> luck.
No, I think that parsing the preprocessor's output for my needs - is
easy. Fact is, I already do that.

>
> > Does doxygen build the partial or the full inclusion tree? (meaning,
> > does it discard the additional includes past the first one? )
>
> It generates a more or less local tree for every file with clickable
> links, so basically it generates a distributed inclusion DAG.
> Additionally it generates the reverse information as well, which other
> files include the particular header, indirectly.
>
> I think full inclusion DAGs are pretty hard to display, because there
> will be too many crossings of the edges in general, so they are of
> limited use, anyway. For visible display local graphs will be of much
> more interest.
You're probably right, but I don't need the visible display... :)
I need the inclusion tree per compiled file, that's all.

>
> Bernd Strieder

Oh well, I guess I'll just waver that desire of mine. Whatever I'm
doing is functional as is. I was trying to solve future problems...
Thanks a lot anyway!
I really appreciate you taking the time to try and help :)
- Tali



reply via email to

[Prev in Thread] Current Thread [Next in Thread]