RFR 8160127, et. al.: JShell API: ExecutionControl implementation support
jan.lahoda at oracle.com
Fri Jul 15 20:05:40 UTC 2016
Seems reasonable to me.
On 15.7.2016 09:31, Robert Field wrote:
> In response to concerns about the logging mechanism, it has been
> removed. Leaving room the standard logging to be used.
> In response to concerns about dependencies on jdk,jshell,
> ExecutionEnv.state() has been removed (this is possible because of the
> JShell-specific logging was removed).
> In response to extensibility concerns, there is now
> ExecutionControl.extensionCommand(), a new exception
> ExecutionControl.NotImplementedException, and RemoteCodes returns with
> string commands.
> In response to the desire to have additional multiplexed channels and to
> multiplexing, System.out and System.err are no longer special-cased, and
> now symmetric stream maps configure both sides.
> JShell API: extract abstract JDI and abstract streaming
> implementations of ExecutionControl
> JShell API: Reorganize execution support code into
> jdk.jshell.execution (previously sent for review, and combined here)
> JShell API: extract abstract streaming remote agent
> Parent bug:
> Specifically --
More information about the kulla-dev