Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 58736 invoked from network); 29 Mar 2008 14:29:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Mar 2008 14:29:12 -0000 Received: (qmail 17402 invoked by uid 500); 29 Mar 2008 14:29:11 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 17368 invoked by uid 500); 29 Mar 2008 14:29:11 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 17359 invoked by uid 99); 29 Mar 2008 14:29:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Mar 2008 07:29:11 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of alexei.fedotov@gmail.com designates 66.249.92.172 as permitted sender) Received: from [66.249.92.172] (HELO ug-out-1314.google.com) (66.249.92.172) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Mar 2008 14:28:27 +0000 Received: by ug-out-1314.google.com with SMTP id u40so82671ugc.3 for ; Sat, 29 Mar 2008 07:28:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=cVGjndD22RzIPPXzfx3V6HI1OhicoukqCrfVUzNkqL4=; b=adIUWjgAlGo1CcGr61oJeRmW68ht7a4MNwqq0MU2ei4dkzBIJNbo9tH5BBMkuNNBw2bDfE7XpFVI68Av+YNoNrMk3dzvQsZygVWnn0i5oQ10ugFy2PGISsN4nIshcLIvrlODMgTvkXMVdTLh1zItRXIdzFNw8MouZ5PjFJu7m8Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=sLQGKu9edMiVeEVGh5cG/3ddE9WRoK5a9i7QJaxTTpe4bmUKNzv96kaC1WEO4VON+wqZa2mEVTi0wBitVOQIaB96oPck3aKVqf7DG/fqD4zH/K7lKAAtUhTYHmG+QAi1XSabHFddsinmc39XDrMdgnSpLKZxzQHMDPR0xs7+5j8= Received: by 10.66.237.14 with SMTP id k14mr626597ugh.72.1206800916190; Sat, 29 Mar 2008 07:28:36 -0700 (PDT) Received: by 10.67.21.8 with HTTP; Sat, 29 Mar 2008 07:28:36 -0700 (PDT) Message-ID: Date: Sat, 29 Mar 2008 17:28:36 +0300 From: "Alexei Fedotov" To: dev@harmony.apache.org Subject: What should we choose for Harmony: JavaCC or AntLR? Was: Google Summer of Code and Harmony MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org Hello, Aleksey, This is a good question indeed. Currently both popular parser generators, i.e. JavaCC and ANTLR, are used in Harmony. We have to decide which one is the preferable one for your project and overall. I believe people who have some experience may help us to decide what suits RTF parser and Harmony better. For your application you may just note that you are collecting arguments to choose one generator from two to be most applicable for Harmony instead of naming the only one, and list the arguments you have already collected. The licensing of both generators is acceptable. I have heard recent talks about incompatible change of AntLR license, and cannot confirm that. It seems that AntLR 3.0 uses conventional BSD license [1]. JavaCC has a proprietary origin [2], but Sun does not claim its rights for this generator. There was a conflict between ANTLR from our boot class path and the one from Dacapo benchmark. I don't think this should be a problem for RTF parser: one can load classes into another class loader. Vladimir Beliaev, Paulex and Alexey Varlamov have to say more about this [3]. >From the other side people said that ANTLR provides more understandable syntax that JavaCC [4], and AFAIK your mentor devoted his university studies to ANTLR. Alexei, all, do you have a parser generator preference? [1] http://www.antlr.org/license.html [2] http://markmail.org/message/v62n2jt7hvb234fi [3] http://markmail.org/message/ja64toonfbo26yz5 [4] http://www.theserverside.com/news/thread.tss?thread_id=45464#233154 On Sat, Mar 29, 2008 at 2:01 AM, Aleksey Lagoshin wrote: > Thanks for links and additional information. > > I noticed that CSS parser is created by JavaCC. As far as I know there is > another one parser generator - ANTLR. So the question is: which tool is more > > preferred/better JavaCC or ANTLR? > > > 2008/3/28, Tim Ellison : > > > > > > Alexei Fedotov wrote: > > > Hello Aleksey, > > > That's great that you appeared on the list. That is nice to chat on > > > GTalk, but the list is preferred. People tend to think thoroughly > > > before sending their letters, so the communication become more > > > thoughtful and transparent. Please, don't hesitate to ask questions on > > > the list: UK guys provide us an object lesson in English courtesy > > > here. > > > > > > LOL, yeah, not like those brash American-types ;-) > > > > > > > I'm happy that you are ok with RTF editor task. From mentor's FAQ it > > > reads that getting two dependent projects accepted is harder than > > > different projects. > > > > > > I think we just need the grammar, look at [1] for the CSS grammar. > > > > We already looked at one [2] contribution for RTF but the license does > > not allow us to incorporate it into Harmony. We need an equivalent to > > that (but don't derive it from this version). > > > > [1] > > > > http://svn.apache.org/viewvc/harmony/enhanced/classlib/trunk/modules/swing/src/main/java/common/org/apache/harmony/x/swing/text/html/cssparser/CSSGrammar.jj?view=markup > > [2] http://issues.apache.org/jira/browse/HARMONY-3898 > > > > > > Regards, > > > > Tim > > > > > > -- > Thanks, > Aleksey > -- With best regards, Alexei