Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 90861 invoked from network); 11 Jul 2006 11:56:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 Jul 2006 11:56:44 -0000 Received: (qmail 11234 invoked by uid 500); 11 Jul 2006 11:56:36 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 11181 invoked by uid 500); 11 Jul 2006 11:56:36 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Received: (qmail 11153 invoked by uid 99); 11 Jul 2006 11:56:36 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jul 2006 04:56:36 -0700 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [206.190.53.30] (HELO smtp105.plus.mail.re2.yahoo.com) (206.190.53.30) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 11 Jul 2006 04:56:35 -0700 Received: (qmail 72453 invoked from network); 11 Jul 2006 11:56:13 -0000 Received: from unknown (HELO ?192.168.1.100?) (dmsmith555@71.64.157.245 with plain) by smtp105.plus.mail.re2.yahoo.com with SMTP; 11 Jul 2006 11:56:13 -0000 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <44B32662.4070701@apache.org> References: <20060707171755.28310.qmail@web50314.mail.yahoo.com> <44AF2284.4040900@manawiz.com> <44AFE036.6020408@apache.org> <44B32662.4070701@apache.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4F01D03D-6483-4441-9EC9-B7A8B98F8951@gmail.com> Content-Transfer-Encoding: 7bit From: DM Smith Subject: Re: Java 1.5 (was ommented: (LUCENE-565) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)) Date: Tue, 11 Jul 2006 07:56:11 -0400 To: java-dev@lucene.apache.org X-Mailer: Apple Mail (2.752.2) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Jul 11, 2006, at 12:17 AM, Daniel John Debrunner wrote: > Doug Cutting wrote: > >> Since GCJ is effectively available on all platforms, we could say >> that >> we will start accepting 1.5 features when a GCJ release supports >> those >> features. Does that seem reasonable? > > Seems potentially a little strange to me. Does this mean Lucene > would be > limited to the set of 1.5 features actually implemented by GCJ? So if > there is a 1.5 feature that is not supported by GCJ (while others are) > it cannot be used? > > Seems more natural to support the complete 1.5 as defined by Sun/Java, > not the subset implemented by one open source compiler. > Eclipse has a built in compiler called ecj and it can compile Java 1.6 code today. However, unless classes are provided at runtime for linking, one will get build errors. The same is true with gcj. It still does not fully support Java 1.4, (almost there...) classes, though it supports all language features. However, on Fedora, Eclipse is built with ecj and to me this demonstrates that it is close enough for most use cases. Gcj will have support for the language features before it supports all the new classes. In terms of Lucene, I believe that the most important classes that are wanted are the concurrency ones. (At least that is how I have read the posts here.) I think the measure of readiness is not that it compiles today with gcj, but that the Java 1.5 classes and features that are likely to be used by lucene are implemented and pass all lucene tests. --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org