Connor Jakubik

The same code parsed fine with `_MSC_VER` `1927` on non-UE4 cmake build of this. I wonder what in the UE4 compile is still messing with this.

Recompiling after changing every `_MSC_VER > 1916` in `tz.h` to `_MSC_VER > 1927` or even `_MSC_VER > 1999` didn't change my compile errors at all. I think I was able...

Putting this at the top of `tz.h`: ```C++ //https://stackoverflow.com/a/53489447 #pragma message("_MSC_VER is " _CRT_STRINGIZE(_MSC_VER)) #pragma message("_MFC_VER is " _CRT_STRINGIZE(_MFC_VER)) #pragma message("_ATL_VER is " _CRT_STRINGIZE(_ATL_VER)) #pragma message("WINVER is " _CRT_STRINGIZE(WINVER)) #pragma...

Even changing all the lines of ```C++ #if !defined(_MSC_VER) || (_MSC_VER > 1916) ``` which show up around the zoned_time restrictions, to ```C++ #if false ``` does not change the...

There's probably some complex complication happening because I do the following strange things: - Link the Not-UE4-compiled date-tz library (Privately) to an API library that is then linked into the...

It's a good thing `zoned_time` is well-encapsulated; I am going forward with the current state of the compiled library without `zoned_time` at the moment (I don't have much of an...

I want to make use of the UTC, TAI, GPS, etc time conversions, so I still need `tz`.

This is already possible if you `#define` the `INSTALL` macro before you `#include "date/tz.h"`. You can also use a CMake function to declare that variable as well in your own...

You have to go to the `chrome://extensions` page to get the proper option to show. I made the mistake of going to a different options screen.

https://github.com/users/Auburn/projects/1#card-49182907 It's on the todo list. I am also eager to see this implemented, and willing to help. @Auburn what all is involved in refactoring for double-precision input functions?