downsides of ASM7_EXPERIMENTAL

i have a fork of kilim (a continuations / actors library for java) that
uses asm (and asm-tree) to weave the bytecode to expose the stack. i
support java 7, 8, 9, 10, and 11 using several different artifacts (i can't
use maven scopes because kilim is also a plugin for AOT weaving)

i currently have an artifact for java 11 that uses ASM7_EXPERIMENTAL and
handles nestmates (but not condy). it is still compiled with java 8, and in
all other ways is identical to the artifact that handles java 8 and 9
(there's an openjdk bug in java 10 that i need to workaround until 10.3, so
it has it's own artifact). all artifacts currently use 6.2.1

i'd like to use ASM7_EXPERIMENTAL for all versions of java (of course,
switching to ASM7 in a few weeks when it's released). i've looked at the
source code and i don't see any uses that would be triggered by class files
generated by java versions 10 or older

my fork of kilim is still a pre-release (it should be promoted to the
official kilim 2.0 soon), so i'm willing to take some risk, but don't want
to ignore anything that's known to be a problem

am i missing anything ? are there any known (or known to be likely)
downsides of ASM7_EXPERIMENTAL when modifying bytecode generated by older
versions of java ?


-- 
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws