You're right. The approach I was suggesting would be to revisit
(remove) the requirement for type safety when using 1.4, but keep it
when using the Java 5 based API. This might be ok as a compromise.
What do you all think?
Cheers,
Jeremy
On 9/8/06, John Kaputin <[EMAIL PROTECTED]> wrote:
That might help with the coding of the internals, but not at the API where
we have an explicit goal of type safety, so our Java 1.4 approach for
collections is typed arrays, not untyped Lists. Sounds interesting though -
thanks for the links.
John Kaputin
"Jeremy Hughes"
<[EMAIL PROTECTED]
rg> To
Sent by: [email protected]
[EMAIL PROTECTED] cc
om
Subject
Re: Java 5 code used in branch
08/09/2006 11:54 WODEN-44
Please respond to
[EMAIL PROTECTED]
he.org
At ApacheCon I saw a nice talk from Torsten Curdt [1] about bytecode
manipulation. He talked a bit about Retroweaver [2] which is able to
create Java 1.4 bytecode from Java 5 bytecode. So I thought it would
be good to investigate whether we could have the type safety of v5
using generics in the source then in the build process generate a
woden.jar for 1.4 bytecode and a woden.jar for v5 bytecode.
What I believe will happen (although I need to verify this by trying
it out!) is projects using the woden.jar with v5 bytecode will get the
typesafety of v5 generics and see that type safety at compile time
e.g. List<Binding>. Projects using the woden.jar with v1.4 bytecode
will get just a List.
I noticed recently the Abdera project (also in incubator) is using
Retroweaver for something - not sure what though.
[1]
http://vafer.org/pub/presentations/apachecon%20EU%202006%20-%20bytecode.pdf
slide 37
[2] http://retroweaver.sourceforge.net
Cheers,
Jeremy
On 9/8/06, Oshani Seneviratne <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On 9/7/06, John Kaputin <[EMAIL PROTECTED]> wrote:
> >
> > Could you please change the relevant code to Java 1.4 compliant for
now?
> >
>
> I made the changes and committed the code. It's at revison 441372.
>
> Thanks,
>
> Oshani
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
