Return-Path: Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org Received: (qmail 39710 invoked from network); 7 Nov 2006 16:34:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Nov 2006 16:34:39 -0000 Received: (qmail 4923 invoked by uid 500); 7 Nov 2006 16:34:47 -0000 Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org Received: (qmail 4894 invoked by uid 500); 7 Nov 2006 16:34:47 -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 4885 invoked by uid 99); 7 Nov 2006 16:34:47 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Nov 2006 08:34:47 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of miguel.montes@gmail.com designates 64.233.162.195 as permitted sender) Received: from [64.233.162.195] (HELO nz-out-0102.google.com) (64.233.162.195) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Nov 2006 08:34:33 -0800 Received: by nz-out-0102.google.com with SMTP id z6so1118049nzd for ; Tue, 07 Nov 2006 08:34:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=Y/BI5HTZq/DRale7Xd9pGiDiKT9hkBd8xYGlxz+rTHqFNUL3313EqLh5nAdYNCu/mOki1EGZVOSpe153MnLMjcLM7Xifxp8tpE848wtQauVFKV3Sxj++hTs2qrcJ9zaG/+x9npTfzRQKIxjEcTsDLLYxcqQhjRNY4y1YQ+nWzk8= Received: by 10.35.113.12 with SMTP id q12mr13305284pym.1162917249268; Tue, 07 Nov 2006 08:34:09 -0800 (PST) Received: by 10.35.109.11 with HTTP; Tue, 7 Nov 2006 08:34:09 -0800 (PST) Message-ID: <9b6bea40611070834m74bca529v3b936002f04ee198@mail.gmail.com> Date: Tue, 7 Nov 2006 13:34:09 -0300 From: "Miguel Montes" To: harmony-dev@incubator.apache.org Subject: Re: [compatibility] Compatibility guideline and HARMONY-2085 In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_9984_20604267.1162917249119" References: <4d0b24970611070712n57564f8brac02848d73913394@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_9984_20604267.1162917249119 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Alexey: Although it's no big deal, I think is useful to be compatible with the RI in this issue. The RI version is simpler, and doesn't expose the internal representation. On 11/7/06, Alexey Petrenko wrote: > > 2006/11/7, Andrew Zhang : > > On 11/7/06, Alexey Petrenko wrote: > > > > > > Guys, > > > > > > have we agreed on toString compatibility? Our compatibility guideline > > > [1] says nothing about compatibility of toString results... > > iirc, Geir has asked SUN about toString issue, and we have no problem to > > keep the same string as RI's. To avoid unnecessary compatibility > problem, > > we'd better return the same value, and we also agreed to do this job > > lazily. :) > Right! Now I recall that thread. > Thanks, Andrew. > > SY, Alexey > > > I think that we do not *need* to follow the RI in this case. Since > > > toString results are not documented and it will be strange to see an > > > application which is rely on them. Or we can discuss each case. > > > > > > Thoughts? > > > > > > The second question: should we apply the patch from HARMONY-2085 [2] > > > which just makes javax.swing.text.html.parser.Element.toString() > > > method compatible with RI. > > > > > > SY, Alexey > > > > > > [1] > > > > http://incubator.apache.org/harmony/subcomponents/classlibrary/compat.html > > > [2] http://issues.apache.org/jira/browse/HARMONY-2085 > > > > > > > > > > > -- > > Best regards, > > Andrew Zhang > > > > > -- Miguel Montes ------=_Part_9984_20604267.1162917249119--