No objections to doing this... but I do object to making
any formal statements that we will keep 1.3 compatiblity.
I certainly don't want to keep remembering which new 
methods, etc, can or can't be used as I code.  

In other words, submissions don't have be 1.3 compatible
but patches to support 1.3 compatiblity are fine.  We don't
state or test for 1.3 compatiblity in releases, but loosely 
try not to prevent it from being possible.

One other question, there's compile compatibility and there's
runtime compatibility.  Are all our dependencies still 1.3 
compatible?

> -----Original Message-----
> From: Thomas Fischer [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, August 15, 2007 5:52 AM
> To: Apache Torque Developers List
> Subject: Re: Generated classes compatible with Java 1.3?
> 
> Anybody any objections about changing this to make us 
> 1.3-compatible again
> ? I'd offer to do it.
> 
>    Thomas
> 
> Thomas Vandahl <[EMAIL PROTECTED]> schrieb am 15.08.2007 11:41:01:
> 
> > Thomas Fischer wrote:
> > > I thought the generated classes were JDK 1.3-compatible. There was
> never an
> > > explicit decision to abandon 1.3 compatibility, as far as 
> I know. What
> are
> > > the problems with 1.3 ?
> > > The syntax is nearly the same as 1.4, so if we support jdk 1.4, we
> should
> > > easily be able to support 1.3
> >
> >
> > I found a RuntimeException(Exception) constructor (probably 
> introduced
> > by myself) in Peer.vm and a couple of Boolean.valueof(boolean) in
> > Object.vm/ObjectWithManager.vm
> >
> > Bye, Thomas.
> >
> > 
> ---------------------------------------------------------------------
> > 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]
> 
> 
DukeCE Privacy Statement:
Please be advised that this e-mail and any files transmitted with
it are confidential communication or may otherwise be privileged or
confidential and are intended solely for the individual or entity
to whom they are addressed. If you are not the intended recipient
you may not rely on the contents of this email or any attachments,
and we ask that you please not read, copy or retransmit this
communication, but reply to the sender and destroy the email, its
contents, and all copies thereof immediately. Any unauthorized
dissemination, distribution or copying of this communication is
strictly prohibited.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to