Re: Dynalink and delete

I’d love to learn more about how you are using Nashorn and Dynalink for teaching, if you can spare a time for a short write-up. Thanks, Attila. > On 2017. Dec 22., at 0:16, Marc Downie wrote: > > > Attila, > > Followed the reviews and commits with anticipation, pulling the changes and > b

Re: Dynalink and delete

Attila, Followed the reviews and commits with anticipation, pulling the changes and building this evening. Assuming it all goes well, I'll have it in front of students writing code in two weeks time. Many thanks! Marc. On Thu, Dec 21, 2017 at 2:59 PM, Attila Szegedi wrote: > Hi Marc, > > So…

Re: Dynalink and delete

Hi Marc, So… this took about a year and a half to happen, but I’m happy to announce that there’s now a REMOVE operation in Dynalink. The latest EA of JDK10 contains it:

Re: Dynalink and delete

There is a not-so-pretty workaround though. Nashorn routes delete on jdk.nashorn.api.scripting.JSObject instances to removeMember method. If you can wrap your Java objects as JSObjects [ may be just for delete], then you can customize delete on your objects. var myJavaObj = ; // myJavaObj is

Re: Dynalink and delete

I recall that we did discuss about the StandardOperation set. "delete" and "iterator" were discussed at one point. But, languages are very different and difficult to generalize to include all operations. For eg. Python's del does not return boolean, ECMAScript delete returns boolean and sometime t