On Wed, 6 Dec 2023 08:14:05 GMT, Alan Bateman wrote:
>> Currently, Locale-related system properties, such as `user.language` or
>> `user.country`, are initialized when the `Locale` class is loaded. Making
>> them static properties is safer than relying on the `Locale` class loading
>> timing,
On Wed, 6 Dec 2023 02:14:13 GMT, David Holmes wrote:
> I'm not following the changes to cdsHeapVerifier.cpp. You've marked the new
> entries as `C` but the definition is:
>
> ```
> // [C] A non-final static string that is assigned a string literal during
> class
> // initialization; this
On Tue, 5 Dec 2023 23:04:55 GMT, Naoto Sato wrote:
> Currently, Locale-related system properties, such as `user.language` or
> `user.country`, are initialized when the `Locale` class is loaded. Making
> them static properties is safer than relying on the class initialization
> timing, which
On Tue, 5 Dec 2023 23:04:55 GMT, Naoto Sato wrote:
> Currently, Locale-related system properties, such as `user.language` or
> `user.country`, are initialized when the `Locale` class is loaded. Making
> them static properties is safer than relying on the class initialization
> timing, which
On Tue, 5 Dec 2023 23:04:55 GMT, Naoto Sato wrote:
> Currently, Locale-related system properties, such as `user.language` or
> `user.country`, are initialized when the `Locale` class is loaded. Making
> them static properties is safer than relying on the class initialization
> timing, which
On Tue, 5 Dec 2023 23:04:55 GMT, Naoto Sato wrote:
> Currently, Locale-related system properties, such as `user.language` or
> `user.country`, are initialized when the `Locale` class is loaded. Making
> them static properties is safer than relying on the class initialization
> timing, which
Currently, Locale-related system properties, such as `user.language` or
`user.country`, are initialized when the `Locale` class is loaded. Making them
static properties is safer than relying on the class initialization timing,
which could potentially be changed depending on the implementation.
