Looks like a but with XL C++. I would open a case with IBM > xlC -o posts posts.cpp && ./posts blah blah, Built Jul 2 2023 10:51:48, Source timestamp Mon Jan 1 0:00:01 1990
> ibm-clang++64 -o posts posts.cpp && ./posts blah blah, Built Jul 2 2023 10:52:08, Source timestamp Sun Jul 2 10:49:43 2023 > On 2 Jul 2023, at 5:52 am, Charles Mills <charl...@mcn.org> wrote: > > I am using XLC __TIMESTAMP__ for the first (!) time. The source file is in > UNIX and definitely has a timestamp. Here is the code > > static const char versionMsg[] = "blah blah, Built " __DATE__ " " __TIME__ ", > Source timestamp " __TIMESTAMP__ ; > > The message is displaying as > > blah blah, Built Jul 1 2023 14:12:35, Source timestamp Mon Jan 1 0:00:01 > 1990 > > There is one i#include ahead of the char[] and it is also a UNIX file with a > timestamp. > > The exact same code works as expected on Windows. > > What am I doing wrong or missing? > > Charles > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
