Do not use facilities provided by the <atomic> header (n2427), (n2752); instead, use the HotSpot Atomic class and related facilities.
Atomic operations in HotSpot code must have semantics which are consistent with those provided by the JDK's compilers for Java. There are platform-specific implementation choices that a C++ compiler might make or change that are outside the scope of the C++ Standard, and might differ from what the Java compilers implement.
In addition, HotSpot Atomic has a concept of "conservative" memory ordering, which may differ from (may be stronger than) sequentially consistent. There are algorithms in HotSpot that are believed to rely on that ordering.
The use of uniform initialization (n2672), also known as brace initialization, is permitted.
+Some relevant sections from cppreference.com:
+Although related, the use of std::initializer_list remains forbidden, as part of the avoidance of the C++ Standard Library in HotSpot code.
The index is included in this exception's detail message. The + * exact presentation format of the detail message is unspecified. + * + * @param index the illegal index. + * @since 16 + */ + public IndexOutOfBoundsException(long index) { + super("Index out of range: " + index); + } } diff --git a/src/java.base/share/classes/java/lang/Module.java b/src/java.base/share/classes/java/lang/Module.java index c1452c098b6..e501094ca93 100644 --- a/src/java.base/share/classes/java/lang/Module.java +++ b/src/java.base/share/classes/java/lang/Module.java @@ -1077,9 +1077,9 @@ public boolean canUse(Class service) { *
For named modules, the returned set contains an element for each * package in the module.
* - *For unnamed modules, this method is the equivalent to invoking the - * {@link ClassLoader#getDefinedPackages() getDefinedPackages} method of - * this module's class loader and returning the set of package names.
+ *For unnamed modules, the returned set contains an element for + * each package that {@link ClassLoader#getDefinedPackages() has been defined} + * in the unnamed module.
* * @return the set of the package names of the packages in this module */ @@ -1094,11 +1094,11 @@ public SetThere are a few standard system properties used to +
+There are a few standard system properties used to alter the mechanisms and behavior of the various classes of the java.net package. Some are checked only once at startup of the VM, and therefore are best set using the -D option of the java command, @@ -38,7 +39,8 @@
If there is no special note, a property value is checked every time it is used.
++If there is no special note, a property value is checked every time it is used.
Since these 2 properties are part of the security policy, they are not set by either the -D option or the {@code System.setProperty()} API, instead they are set as security properties.
+ ++Calling {@link java.nio.channels.ServerSocketChannel#bind(SocketAddress,int) ServerSocketChannel.bind} +with a {@code null} address parameter will bind to an automatically assigned socket address. +For Unix domain sockets, this means a unique path in some predefined system temporary directory. +There are a number of system (and networking) properties that affect this behavior. +
+Unix domain socket addresses are limited in length to approximately 100 +bytes (depending on the platform), it is important to ensure that the temporary directory's name +together with the filename used for the socket (currently a name similar to +{@code socket_1679697142}) does not exceed this limit. The following properties +can be used to control the selection of this directory: +
+
{@systemProperty jdk.net.unixdomain.tmpdir} This can be set as + a networking property in {@code conf/net.properties} If set, this specifies the + directory to use for automatically bound server socket addresses. On some platforms, + (eg some Unix systems) this will have a predefined default value. On others, + (eg Windows) there is no default value. Either way, it is always possible + to override the networking property with a system property of the same name + set on the command line. If neither of the networking nor system property + are set, then some systems (eg Windows) may check a commonly used environment + variable as temporary directory. +
{@systemProperty java.io.tmpdir} If the previous step fails to locate + a directory to use, then the directory identified by the system property + {@code java.io.tmpdir} is used. +
+Implicit binding of a {@link java.nio.channels.SocketChannel SocketChannel} +
+If a client socket is connected to a remote destination without calling {@code bind} first, +then the socket is implicitly bound. In this case, Unix domain sockets +are unnamed (ie. their path is empty). This behavior is not affected by any +system or networking properties. +
{@systemProperty jdk.includeInExceptions} This is typically set to + a comma separated list of keywords that refer to exception types whose messages + may be enhanced with more detailed information. If the value includes the string + {@code hostInfo} then socket addresses will be included in exception message + texts (eg hostnames, Unix domain socket address paths). +