Chris Quenelle wrote: > I've attached an answer from the C++ compiler team lead. > I don't think it's much help. > > All I can think of is wrapping the compiler driver with a script > that LD_PRELOADs an interposer on gettimeofday() > (or whatever the appropriate libc call is). > > You know. The usual hack. But maybe sed scripts are easier. > It certainly seems like a good RFE if you're interested in a more > long-term solution. > >> Someone could file an RFE asking for the rule to be relaxed. We could >> downgrade the error to a warning, and the normal message-suppressing >> options would eliminate the warning. We would still be in violation of >> of the "constant value" provision, so I think modifiability would have >> to be controlled by an option.
I'll file an RFE... 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. - Bart -- Bart Smaalders Solaris Kernel Performance barts at cyber.eng.sun.com http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird."
