Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
12.6beta tested for compatibility with Howard Hinnant's date and time library

Has 12.6beta been tested in building Howard Hinnant's date and time library?
I tried building the library using 12.5 without success.
Answers
-
We do not test with that library.
I can't speak about that library in particular, but most problems building open source with Studio are due to Studio not being recognized, or being used with incorrect command-line options, or using workarounds for old Studio compilers that are no longer appropriate.
Look for conditional code like
#if <apple>
...
#elif <gnu>
...
#elif <microsoft>
...
#endif // Studio is none of the above
Also look for conditional code like
#If <studio>
... non-standard code that doesn't work with modern Studio compilers
#else
... standard code
#endif
If you post specific problems, I might be able to help.
-
Hi,
Howard Hinnant's date and time library is a proposed extension to the std::chrono library which enables C++ to handle calendars and timezones.
The one I'm using is his proof-of-concept implementation which is reliant on a compiler which has high C++14 compliance.
I was attempting to build the library with Developer Studio 12.5 in C++14 mode and providing feedback to Howard Hinnant himself. However, I got stuck and unable to figure out the issues the compiler was complaining about. I'm hoping that a newer version of the compiler with better C++14 compliance will resolve the issues.
BTW, my own library is dependent on C++14 features thus I decided to wait until Developer Studio's C++14 compliance gets better thus I will get back to it once you release Developer Studio 12.6.
-
Hi,
I have tried building Howard Hinnant's date and time library again with Developer Studio 12.6.
According to the built-in macros with the C++ compiler in this version of Developer Studio, it is C++14 compliant however it still unsuccessfully builds the said library.
This library checks the value of __cplusplus to determine its constexpr awareness and it seems to be picking up the correct branch in the code.
I would love to supply a .tar.gz file that contains everything I'm using to do the abovementioned build but could not figure out how to attach it to this message.
Kind regards,
Leo
-
As shown in the "What's New" document for Studio 12.5,
https://docs.oracle.com/cd/E60778_01/html/E60742/gncix.html#scrolltoc
support was available only for only a few minor C++14 features.
Studio 12.6 nominally provides full support for C++14, but some features have bugs. Some bugs did not show up until it was too late to fix them for the release. You might be running into a one of them. Or this library might trigger a bug we haven't yet seen.
I'll talk with Howard directly and see what we can find out.
-
You didn't say what parts of the library you tried, so I downloaded the current master version and tried two simple test cases, with the following results.
1. Oracle Developer Studio compilers predefine by default some nonstandard macros, "sun" in particular, which conflicts with an identifier in the source code.
Solution: Compile with the "+p" option, which prevents macros in the user's namespace from being predefined.
2. "date.h" seems to work in C++11 mode, but not in C++14 mode, due to bugs in the compiler's handling of constexpr. We plan to fix the constexpr bugs.
3. Compiling tz.cpp in C++11 mode ran into an error with one of the standard C++ headers. Either we have an issue with our version of the g++ headers, or there is a compiler bug. Due to this problem, I did not try C++14 mode. I will file an internal bug for the header problem.
-
I was trying to build tz.cpp into a shared library using C++14 mode and as you mentioned, my build was having constexpr issues in relation to the weekday constants in date.h and in some other areas.
When I try C++11 mode, another issue shows up to do with std::enable_if_t.
You mentioned the sun macro. This was why I couldn't figure out why my build was having issues with the definition of the constant for Sunday.
-
Forget my comment concerning std::enable_if_t. That was me making the wrong changes in the source code.
However, I tried +p option and compiled in C++11 mode and the only issue I found is to do with tuple/unique_ptr in tz.cpp.
I hope we had observed the same issue.
Will the fixes be issued as a patch or will go into the next release?
-
Compiling tz.cpp in C++11 mode, I found 3 errors similar to this one:
"/.../CC-gcc/include/c++/5.4.0/tuple", line 62: Error: Using deleted function 'date::{lambda at tz.cpp,2620:33}::<constructor>()'.
These errors are due to a compiler bug not previously seen.
I did not try C++14 mode, since tz won't compile anyway, and we have known constexpr issues to fix.
If you have a Studio service contract with Oracle, you can request via your support channel that all bugs preventing compilation of the date library be fixed in a patch.
We hope to fix these bugs anyway, but Oracle policy does not allow me to be more specific.
-
FYI, Howard Hinnant has made the necessary changes to the library based on feedback supplied to him to allow the library to build correctly in either C++11 or C++14 modes with Developer Studio 12.6 on Oracle 11.3 x86_64.