JEP 222: Java Read-Eval-Print Loop (REPL)
forax at univ-mlv.fr
Sat Nov 1 21:45:37 UTC 2014
On 11/01/2014 05:14 PM, Brian Goetz wrote:
> What might be useful, though, is any *usability* experience that you
> had with people trying it out. What did people complain about? What
> non-obvious features did people seem to expect should be part of the
> feature set?
I build 3 REPLs for mostly DSLs that runs on top of the JVM.
features: history, code completion, doc, record/replay
- number 1: it works in the REPL but not with a file.
- number 2: can I avoid to declare the types (see number 1).
- it doesn't work like bash, zsh, ipython.
- can I have the feature XXX of IntelliJ/Eclipse/Netbeans ?
- the doc of this method is too big, I want only the interesting part.
- record/replay, I want only to replay the part that are not me
> (Note, though, that we're asking for *actual* experience of "I built X
> and people who used it complained of Y", not theorizing of the form "I
> could imagine I might want Y in some situation...".)
> On 11/1/2014 12:03 PM, Robert Field wrote:
>> Thanks Bruce. I'm quite far along, so I doubt that would be useful.
>> On 11/01/14 01:58, Bruce Chapman wrote:
>>> I built (for some value of "built" near to the value of "hack") one of
>>> these back in 2009 for our local java user group  as a demo for the
>>> compiler API and an annotation processor test framework I built 
>>> If you are interested I can find and dust off the code and make sure
>>> it still all works (why wouldn't it).
>>>  http://wellingtonjug.org.nz/talk200905.html
>>>  https://java.net/projects/hickory
>>> On 31/10/2014 10:56 a.m., mark.reinhold at oracle.com wrote:
>>>> New JEP Candidate: http://openjdk.java.net/jeps/222
>>>> - Mark
>>> This email is free from viruses and malware because avast! Antivirus
>>> protection is active.
More information about the compiler-dev