(In reply to John Ralls from comment #61)
>
> What were you planning to use for a date type? GLib's GDate? It's the only
> ready-made date implementation I know of that doesn't have a timezone
> problem, but we're trying to move away from GLib in GnuCash's core,
> preferring the C++ standard library. Unfortunately std::chrono is
> time-oriented and its date type is timezone-sensitive, as are
> boost::date_time and ICU's.
I'm not a C++ developer, but isn't this dealt with by the new date operators in std::chrono?
This is discussed in detail in the "Opening Keynote Meeting C++ 2019 - Howard Hinnant - Design Rationale for the chrono Library" at https://youtube.com/watch?v=adSAN282YIw
(In reply to John Ralls from comment #61)
>
> What were you planning to use for a date type? GLib's GDate? It's the only
> ready-made date implementation I know of that doesn't have a timezone
> problem, but we're trying to move away from GLib in GnuCash's core,
> preferring the C++ standard library. Unfortunately std::chrono is
> time-oriented and its date type is timezone-sensitive, as are
> boost::date_time and ICU's.
I'm not a C++ developer, but isn't this dealt with by the new date operators in std::chrono?
https:/ /en.cppreferenc e.com/w/ cpp/chrono/ year_month_ day
This is discussed in detail in the "Opening Keynote Meeting C++ 2019 - Howard Hinnant - Design Rationale for the chrono Library" at https:/ /youtube. com/watch? v=adSAN282YIw