jpackage is not and not planned to be available on Solaris. It is only
on Windows, Linux and Mac. Is this a sufficient argument to bring in the
patch as is and not rework it to make C++98 compliant?
According to the list of supported compilers [1] on platforms where
jpackage is available they all support C++11 for several years already.
[1] https://wiki.openjdk.java.net/display/Build/Supported+Build+Platforms
- Alexey
On 3/3/2020 7:29 PM, Kim Barrett wrote:
On Mar 3, 2020, at 4:49 PM, Alexey Semenyuk <alexey.semen...@oracle.com> wrote:
How about C++11? I have a pending patch for jpackage that depends on C++11
features that I hesitate to pull in jdk15.
The reasons for HotSpot (at least) not already being on C++14 (cost of
switching over the Solaris Studio based platform) also apply to C++11.
A big part of the work involves dealing with changes to the compilation
model, the runtime libraries, and the ABI, all of which are part of
Solaris Studio's transition from C++98 to C++11.
