New candidate JEP: 454: Foreign Function & Memory API

[Pedro Lamarão]

Em sex., 15 de set. de 2023 às 11:48, Rony G. Flatscher <
Rony.Flatscher at wu.ac.at> escreveu:

Actually the code already is able to configure the JVM. However, this can
> be done only, if BSF4ooRexx loads the JVM (and the environment variable
> BSF4Rexx_JavaStartupOptions is set). It cannot be done if the JVM got
> already loaded by someone else and the BSF4ooRexx bridge gets loaded into
> the process.
>

Whoever sets up the JVM must maintain the JVM initialization flags.
This person must add whatever initialization flags are appropriate and/or
required whenever they become appropriate and/or required.
Suppose this person assembles an application including component XPTO, and
this person desires to upgrade XPTO to new version 123 that adds a new
feature that uses the new FFI: during this upgrade, this person also adds
--enable-native-access to the initialization flags, and all is good. If
this person is not aware of this need, it will become aware during testing,
because the JVM will alert of this necessity.
I cannot visualize what hypothetical situation is this in which whoever
assembles the application and sets up the JVM is somehow incompetent or
incapable to apply this change.
Are we considering situations where people blindly upgrade components of
their architecture with no preparation nor testing to only discover the
consequences in production?

-- 
Pedro Lamarão
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/panama-dev/attachments/20230915/2aed25e1/attachment.htm>