> On Jun 8, 2020, at 4:07 PM, Philip Race <philip.r...@oracle.com> wrote: > > Hi Kim, > > Can we amend the JEP itself to be not solely about hotspot. > Since it affects other areas I think that > 1) They may need to be compiled with C++14 enabled whether they use new > features or not > 2) They may want - or need - to adopt C++11 or C++14 features too. > > You already know that soon we will upgrade the harfbuzz 3rd party library > used by 2D > and it will bring along the need to use C++11 features and I had no plan to > propose a JEP for that. > So I don't want to be asked why we didn't do one when hotspot did ! > So this really ought to be a JDK JEP whilst of course explaining that hotspot > is expected > to be the primary adopter.
I think this is at least mostly covered by the following paragraph from the JEP: (This JEP does not propose any usage or style changes for C++ code in the JDK that is outside of HotSpot. The rules are already different for HotSpot and non-HotSpot code. For example, C++ exceptions are used in some non-HotSpot code, but are disallowed in HotSpot by build-time options. However, build consistency requirements will make the newer language features available for use in all C++ code in the JDK.) That’s why I cc’d the RFR to several mailing lists in addition to hotspot-dev. Is there something additional you would like to add? > BTW the JEP (https://bugs.openjdk.java.net/browse/JDK-8208089) still says > > For Solaris: Add the -std=c++14 compiler option. ..... > > So I am sure there is still some room to update the JEP :-) Yeah, I have some updates to make. I also need to do a bit of work on the feature lists.
