- Original Message -
> From: "Jochen Theodorou"
> To: "dev"
> Sent: Sunday, January 28, 2024 10:38:24 PM
> Subject: Re: [EXT] Re: ClassFile API
> On 28.01.24 15:05, Remi Forax wrote:
> [...]
>> Hello,
>> before i answer to your question
classfile API,
you have to manage the fact that a new subtype of a hierarchy can appear in the
next version.
yeah, sorry for confusing you and the limited creativity. I did
understand that.. Maybe I should have taken something else as example
that changes the class level, or members. records would have
- Original Message -
> From: "Jochen Theodorou"
> To: "dev"
> Sent: Sunday, January 28, 2024 1:19:24 PM
> Subject: Re: [EXT] Re: ClassFile API
> On 27.01.24 18:58, Remi Forax wrote:
> [...]
>> The classfile API uses sealed types, once those w
On 27.01.24 18:58, Remi Forax wrote:
[...]
The classfile API uses sealed types, once those will be updated either the
groovy compiler will need to be updated or a default of a switch will be called.
See how the overview of the API uses "default" everywhere.
https://cr.openjdk.or
- Original Message -
> From: "Jochen Theodorou"
> To: "dev"
> Sent: Saturday, January 27, 2024 12:35:40 PM
> Subject: Re: [EXT] Re: ClassFile API
> On 23.01.24 19:33, Milles, Eric (TR Technology) via dev wrote:
>> An API like this works fine f
On 23.01.24 19:33, Milles, Eric (TR Technology) via dev wrote:
An API like this works fine for straightline code. But if you need to add
instructions conditionally, repeat blocks for additional instances, or other
complex scenarios; builders can quickly break down. I would wait to see how
th
hen Theodorou
Sent: Tuesday, January 23, 2024 11:28 AM
To: dev@groovy.apache.org
Subject: [EXT] Re: ClassFile API
External Email: Use caution with links and attachments.
On 22.01.24 01:23, Daniel Sun wrote:
> Hi Jochen,
>
> Groovy relies on ASM lib directly, so it would save lots o
On 22.01.24 01:23, Daniel Sun wrote:
Hi Jochen,
Groovy relies on ASM lib directly, so it would save lots of work if we
could have an abstract layer whose API aligns with ASM lib, just change ASM
package name(org.objectweb.asm) with Groovy package name, e.g.
org.apache.groovy.classfile.
On 22.01.24 20:15, Milles, Eric (TR Technology) via dev wrote:
The new Class File API is for reading not writing, correct?
I had a different impression. Sure, reading is a big use case for normal
Javausers, but they are currently moving their bytecode generation as
well. For example for proxies
There are many bytecode lib in the Java world, an abstract layer for handling
bytecode can prevent Groovy from the change of implementation. It is similar to
system with data persistence layer which provides unified API to access
databases, e.g. MySQL, PostgreSQL, Oracle, etc. If database change
The new Class File API is for reading not writing, correct? With that in mind,
I think only the ASM decompile package (org.codehaus.groovy.ast.decompiled) is
under consideration. There are already 2 paths taken by ClassNodeResolver
tryAsLoaderClassOrScript. Adding a third option there that is
Hi Jochen,
Groovy relies on ASM lib directly, so it would save lots of work if we
could have an abstract layer whose API aligns with ASM lib, just change ASM
package name(org.objectweb.asm) with Groovy package name, e.g.
org.apache.groovy.classfile.
Cheers,
Daniel Sun
On 2024/01/21 13:05
On 20.01.24 17:47, Daniel Sun wrote:
Hi Jochen,
Both ASM lib and Class-File API are good, I would like to have an
abstract layer for them. The API for the abstract layer could be align with ASM
lib as Groovy relies on ASM lib heavily.
If Groovy finds Class-File API is avaible, use
for an abstract layer, otherwise use ASM lib.
Cheers,
Daniel Sun
On 2024/01/18 17:19:07 Jochen Theodorou wrote:
> Hi all,
>
> currently the Classfile API (https://openjdk.org/jeps/457) is getting
> more and more usage in the newest version of the jdk. Even though the
> target is not
Hi all,
currently the Classfile API (https://openjdk.org/jeps/457) is getting
more and more usage in the newest version of the jdk. Even though the
target is not to replace the ASM lib, that is actually happening for the
JDK. As for the motivation of why they move from ASM to the ClassFile
API
15 matches
Mail list logo
