ECJ-INTEREST-L Archives

June 2015

ECJ-INTEREST-L@LISTSERV.GMU.EDU
Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
ECJ Evolutionary Computation Toolkit <[log in to unmask]>
Date:
Sun, 21 Jun 2015 21:01:57 -0400
MIME-version:
1.0 (Mac OS X Mail 7.3 \(1878.6\))
Reply-To:
ECJ Evolutionary Computation Toolkit <[log in to unmask]>
Content-type:
text/plain; charset=us-ascii
Subject:
Re: JRE compatibility
From:
Sean Luke <[log in to unmask]>
In-Reply-To:
<[log in to unmask]>
Message-ID:
<[log in to unmask]>
Content-Transfer-Encoding:
8bit
Parts/Attachments:
text/plain (19 lines) 
I try to be conservative about ECJ's needs, but we can update it if we really  have to.  If you're thinking of submitting changes to ECJ, it'd be nice if it were still compatible with 1.6 unless there was a really good reason to do so.

Sean

On Jun 21, 2015, at 7:32 PM, Eric 'Siggy' Scott <[log in to unmask]> wrote:

> Is the version of Java that ECJ is supposed to remain compatible with still 1.6?
> 
> I've been toying around with some potential changes on a fork, and started to use some Java 7 features by habit (such as a switch on strings).  Should I refrain from doing so?
> 
> Cheers,
> Siggy
> 
> -- 
> 
> Ph.D student in Computer Science
> George Mason University
> http://mason.gmu.edu/~escott8/

ATOM RSS1 RSS2