Mike Strobel

This is _probably_ fixed for the next release (javac changed the pattern it emits for try-with-resources sometime after JDK8).

This is a rather complicated issue that I've only just started addressing. Problem is, the Lookup-based alternative is much more restrictive (by design) and will require some refactoring. I have...

I've been working on Procyon again, after a long hiatus. I'll have a new release ready soon, but I went ahead and uploaded a prelease jar. You can find it...

I’m actually working on this now. Biggest roadblock was `TypeBuilder` in Procyon.Reflection. Aside from some test issues, I seem to have everything compiling and running in both JDK8 and JDK17.

Any chance you can nail down the exact class it fails on? I recently fixed a similar bug, but I'd like to verify.

Oh lord, you've stumbled into Procyon's weakest link--it's exception handler processing. It's pretty broken, and I'm honestly surprised it works as well as it does (most of the time). It's...

Will look into this in greater detail later, but this did catch my eye: I don't think `constant(1.12f, Types.Number)` should be considered valid, and it's not really what the equivalent...

Cool project! You may want to go ahead and check out my `v0.6-staging` branch, as it makes some changes to `TypeBuilder` and `LambdaCompiler` to let them work on JDKs newer...

The problem might be that you're only processing a single class per run, as opposed to decompiling all the classes in a single run. Decompiling even a single class involves...

I suspect this is due to Procyon emitting classes in Java 5 format, which doesn't support static interface methods. Emitting newer classfiles is, unfortunately, quite an undertaking.