<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 5 Mar 2019 at 10:39, Leon Mlakar via Boost-users <<a href="mailto:boost-users@lists.boost.org">boost-users@lists.boost.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div bgcolor="#FFFFFF"><p>Behid the question was my, obviously incorrect, assumption that olde visual studio versions, from times when c++20 was not yet conceived and epoch thus not set to Jan 1 AD 1970, are using some different epoch - as Microsoft frequently did, like Jan 1 AD 1 (.NET), Jan 1 AD 1601 (NTFS),</p></div></blockquote><div>MS just implements the standard [in this case] and for timings within Windows (i..e. Windows.h), they have the FILETIME API, " Jan 1 AD 1 (.NET), Jan 1 AD 1601 (NTFS)", etc (possibly because they realized the world was not created in 1970, but heck who knows).<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><p> Jan 1 AD 1980 (DOS, FAT family of file systems). So seeing Microsoft embracing a standard thing like posix epoch without screaming and kicking is a nice surprise.<br></p></div></blockquote><div>Well at the time of DOS, there was no std, so one could forgive them (on this occasion) to not implement it correctly.</div></div><div class="gmail_quote"><br></div><div class="gmail_quote">degski<br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div><i><b><span><i><b>"Big boys don't cry" - </b></i></span></b></i><i><b><span><i><b>Eric Stewart, Graham Gouldman</b></i></span></b></i></div></div></div></div></div></div></div></div></div>