>>> the use of __TIME__ and __DATE__ means that a build
>>> produces different binaries every single time; this forces engineers to
>>> manually evaluate whether or not a source change (a header file, for
>>> example) affects a given binary.  This induces errors, or forces us to
>>> always ship any binary which has such constructs in the source code,
>>> inflating everyone's costs to no good purpose.
I agree the compiler should have a way to override these macros.

Wouldn't it also be possible to modify the software in question so that
it doesn't
use __TIME__ and __DATE__?

--chris


Reply via email to