Re: Module boundaries with classes and exceptions.
perrog@gmail.com wrote:
[...]
James Kanze skrev:
And how. That and an MD5 hash of the tokens for each class,
definition, inline function and template would sure save a lot
of debugging work.
I don't think this is to far away. GNU's C/C++ pre-compiler and gcc
must handle incompatible compile options in future release, because
there is a strong need for it.
Very. But there's been a strong need for it for quite some time
now; I first encountered the problem over 15 years ago.
Supposing, of course, that "incompatible compile options"
includes things like -DsomethingOrOther. And of course,
ideally, we would prefer if it didn't complain if one module was
compiled with -DNDEBUG, and the others not---although this might
formally result in undefined behavior (due to an inline function
using assert()), it should work in practice. (But such a
distinction may be asking too much.)
--
James Kanze (Gabi Software) email: james.kanze@gmail.com
Conseils en informatique orient?e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S?mard, 78210 St.-Cyr-l'?cole, France, +33 (0)1 30 23 00 34
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]