Return-Path: Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org Received: (qmail 23894 invoked from network); 31 Oct 2006 09:43:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Oct 2006 09:43:00 -0000 Received: (qmail 8083 invoked by uid 500); 31 Oct 2006 09:43:08 -0000 Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org Received: (qmail 8042 invoked by uid 500); 31 Oct 2006 09:43:08 -0000 Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: harmony-dev@incubator.apache.org Delivered-To: mailing list harmony-dev@incubator.apache.org Received: (qmail 8032 invoked by uid 99); 31 Oct 2006 09:43:08 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Oct 2006 01:43:08 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [134.134.136.20] (HELO mga02.intel.com) (134.134.136.20) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Oct 2006 01:42:56 -0800 Received: from orsmga001.jf.intel.com ([10.7.209.18]) by mga02.intel.com with ESMTP; 31 Oct 2006 01:42:35 -0800 Received: from fmsmsx334.amr.corp.intel.com ([132.233.42.1]) by orsmga001.jf.intel.com with ESMTP; 31 Oct 2006 01:42:35 -0800 X-ExtLoop1: 1 X-IronPort-AV: i="4.09,374,1157353200"; d="scan'208"; a="153434946:sNHT19162654" Received: from fmsmsx312.amr.corp.intel.com ([132.233.42.227]) by fmsmsx334.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 01:42:34 -0800 Received: from mssmsx411.ccr.corp.intel.com ([10.125.2.10]) by fmsmsx312.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 01:42:35 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [classlib] Preprocessor Date: Tue, 31 Oct 2006 12:42:26 +0300 Message-ID: <8E389A5F2FEABA4CB1DEC35A25CB39CE695089@mssmsx411> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [classlib] Preprocessor thread-index: Acb8zuXHEmU7mSZZTWC8VXWWF6OhDQAABblA From: "Fedotov, Alexei A" To: X-OriginalArrivalTime: 31 Oct 2006 09:42:35.0019 (UTC) FILETIME=[E4E41DB0:01C6FCD0] X-Virus-Checked: Checked by ClamAV on apache.org Geir, I tried this preprocessor staff for Java in my previous life. From my experience the maintenance effort is higher for this solution than for Source Control. 1. I faced first time how slow regular expressions on Java could be. 2. Perl worked fine but no one around me could understand my pre-processing scripts and maintain them. 3. The girl from Ireland beat my clever scripts with Sun's TeamWare and text editor. +1 for Source Control With best regards, Alexei Fedotov, Intel Java & XML Engineering >-----Original Message----- >From: Geir Magnusson Jr. [mailto:geir@pobox.com] >Sent: Tuesday, October 31, 2006 12:28 PM >To: harmony-dev@incubator.apache.org >Subject: Re: [classlib] Preprocessor > > > >Tim Ellison wrote: >> Mikhail Fursov wrote: >>> What are the reasons to exclude the most standard solution here: >branching. >>> Do you think we need a lot of them? >> >> I don't think we are excluding any option for maintaining similar code >> streams (5.0 & 6.0, SE & ME, etc.) it's just a discussion at the moment. >> >> Similarly, I'm not advocating the use of aspects for maintaining >> different code streams; but rather I was saying that IDE support is >> likely going to be a requirement for any technology (apt, preprocessor, >> post-processing, aspects, ...) that we choose to solve the problem. >> >> I'm sure we wouldn't even want simple branching without a decent merge >> tool to keep things in sync. > >Yes - that's what I'm scared of. A branch solution sounds like it >leads to much misery and woe, because i think all the factors that make >this such an interesting problem for which a pre-processor is a valid >solution this implies the requirement of some kind of conditional merge > >> >> I agree with Geir that we should endeavour to choose a technology that >> has broad tooling support. >> >> Regards, >> Tim >>