On Wed 09 Jun, Jeff Dalton wrote:

> It's hard to see how this can really be a Y2K issue.

Yes, but Y2K compliance (or lack of it) might well affect any fixes for
this problem. The point is that you can't assume that Y2K is a non-issue
for all compilers. Some do use date and time to modify their output. 

Regards
-- 
Adrian Hey



Reply via email to