New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine (original) (raw)
Alan Bateman Alan.Bateman at oracle.com
Fri Jun 15 12:40:22 UTC 2018
- Previous message: New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine
- Next message: New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 15/06/2018 13:25, Attila Szegedi wrote:
: FWIW, @CS is not an issue. Untrusted code can somewhat more weakly detect the @CS annotation by its name instead of by its class. Sure, I'm just pointing out that it currently has both a compile-time and run time dependency on @CS and that would need attention in the event that it were to be jettisoned and maintained outside of the JDK.
BTW: I do think you are are right to ask why jdk.dynalink is listed in JEP 335, that isn't fully explained in the motivation section at this time.
-Alan
- Previous message: New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine
- Next message: New candidate JEP: 335: Deprecate the Nashorn JavaScript Engine
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]