Re: Writing a compiler to handles, but filter seems to executed in reverse

Thanks, IBM!! Filed: https://bugs.openjdk.java.net/browse/JDK-8194554 On Jan 3, 2018, at 12:04 PM, Remi Forax wrote: > > IBM implementation uses the left to right order ! > I've just tested with the latest Java 8 available. > > Java(TM) SE Runtime Environment (build

Re: Writing a compiler to handles, but filter seems to executed in reverse

IBM implementation uses the left to right order ! I've just tested with the latest Java 8 available. Java(TM) SE Runtime Environment (build 8.0.5.7 - pxa6480sr5fp7-20171216_01(SR5 FP7)) IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20171215_373586 (JIT enabled, AOT

Re: Writing a compiler to handles, but filter seems to executed in reverse

On Jan 2, 2018, at 12:35 PM, Charles Oliver Nutter wrote: > > Is there a good justification for doing it this way, rather than having > filterArguments start with the *last* filter nearest the target? No, it's a bug. The javadoc API spec. does not emphasize the ordering of

Re: Writing a compiler to handles, but filter seems to executed in reverse

On Jan 2, 2018, at 12:36 PM, Charles Oliver Nutter wrote: > > An alternative workaround: I do the filters myself, manually, in the order > that I want them to executed. Also gross. (Under the theory that the spec. is ambiguous, leading to implementor's choice, this would be

Re: Writing a compiler to handles, but filter seems to executed in reverse

https://gist.github.com/forax/5d3c68733c4ff39ae20b8bdcfa3d8b0a The general solution for simulating a function call is to use fold and not filter (see line 87), filter only works in your case because you pass all your variables as an array. One interesting remark is that you can not compile