This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: -fdump-translation-unit considered harmful (was Re: cp tree question)



no matter if you should get rid of dump-translation-unit - I was talking about the different behaviour of the cp tree interface between versions.
I'm not trying to read dump-translation-unit output, but you can see what I mean using it because it also uses the tree interface.
so have there been any major changes to this interface lately or should it be reported as a bug when a function which is documented to return all decls of a namespace leaves out some?




Zack Weinberg schrieb:
We should get rid of -fdump-translation-unit.  It has never done what
people think it does, the output format has never been documented, no
one cares to improve either of those things, and we now have
tree-pretty-print.c which is language-independent and far easier to
read.  No, it's not machine parseable, but neither is
-fdump-translation-unit's format, if you really sit down and think
about it.

zw





-- Stefan Strasser


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]