Re: problem in gcc (lib) headers __BEGIN_DECLS & traceback-incomplete

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

 



Jonathan Wakely wrote:

No, it would be better to just improve the diagnostics using some heuristics.
---
	That would be ideal.  I was suggesting something that
might be easier to diagnose, but if it can be done using a heuristic, that would obviously be better.



Simply issuing an error whenever a block isn't closed before a header
would not be conforming, but when the compilation fails anyway the
compiler could check if it happened and say something about it in the
errors.
---
	Absolutely.  If it is going to generate an error anyway,
the the code is "obviously" non-conforming, so conforming-only behavior is no longer the point.





[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux