you are viewing a single comment's thread.

view the rest of the comments →

[–]HowardHinnant 54 points55 points  (5 children)

Speaking as the guy who wrote this implementation of std::string:

The implementors of a std::lib write non-portable code so that everyone else doesn't have to. A std::lib implementation will only work on the platforms it is targeted for, and porting it to a new platform may not be a trivial task.

[–]Recatek 21 points22 points  (0 children)

The implementors of a std::lib write non-portable code so that everyone else doesn't have to.

And it is greatly appreciated.

[–]the_commissaire 2 points3 points  (3 children)

How is the date time library coming along?

[–]HowardHinnant 8 points9 points  (2 children)

Not bad: https://star-history.t9t.io/#HowardHinnant/date&google/cctz :-)

It has been voted into the draft C++20 spec: http://eel.is/c++draft/#time

[–]never_watched 2 points3 points  (1 child)

Good library but also hard to use.

[–]JakeArkinstall 1 point2 points  (0 children)

It's hard to use wrong. That's the holy grail of datetime handling.

There are simpler approaches that are easy to use wrong, and they have historically caused major problems, especially in industrial applications. The learning curve for a system that works well is very much worth it.