From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 948 invoked by alias); 28 Nov 2001 20:36:02 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 905 invoked from network); 28 Nov 2001 20:35:59 -0000 Received: from unknown (HELO bothner.com) (216.102.199.253) by hostedprojects.ges.redhat.com with SMTP; 28 Nov 2001 20:35:59 -0000 Received: from bothner.com (eureka.bothner.com [192.168.1.9]) by bothner.com (8.11.0/8.11.0) with ESMTP id fASKZtM22626; Wed, 28 Nov 2001 12:35:55 -0800 Message-ID: <3C054ABC.6000207@bothner.com> Date: Tue, 20 Nov 2001 23:37:00 -0000 From: Per Bothner User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011120 X-Accept-Language: en-us MIME-Version: 1.0 To: Ziemowit Laski CC: gcc@gcc.gnu.org Subject: Re: Target-specific Front-Ends? (Was: front end changes for References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2001-11/txt/msg01003.txt.bz2 Ziemowit Laski wrote: > I wouldn't mind COLLABORATING with someone on this (I don't think I > have sufficient cycles left in my day to go it alone). But first > and foremost, I'd like to have some sort of a statement from the SC > specifying the technical parameters of an acceptable solution -- > in other words, a guarantee that if a solution meeting those > criteria is created, it will be accepted. Generally the SC defers to the maintainers, especially the more experienced/senior maintainers - some of whom are SC members. In any case I don't think either the SC or the experienced maintainers can make much of a statement "specifying the technical parameters of an acceptable solution", nor can we make any "guarantee that if a solution meeting those criteria is created, it will be accepted". Sorry. Instead, you will have to make a proposal on this mailing list, and achieve a more-or-less consensus that what you're proposing is sufficiently useful and implementable that it makes up for any extra maintainance or compile-time performance problems. > No more Pascal string work from me. :) :) My take on that was that Apple gave up just a little too easily on that, and that we were close to accepting the \p extension. At least I was leaning in favor of it. -- --Per Bothner per@bothner.com http://www.bothner.com/per/ From mboxrd@z Thu Jan 1 00:00:00 1970 From: Per Bothner To: Ziemowit Laski Cc: gcc@gcc.gnu.org Subject: Re: Target-specific Front-Ends? (Was: front end changes for Date: Wed, 28 Nov 2001 12:36:00 -0000 Message-ID: <3C054ABC.6000207@bothner.com> References: X-SW-Source: 2001-11/msg01504.html Message-ID: <20011128123600.VAW4FXXqoxwM9qB7CExUdh7hxwYKXdDny41v2egl84A@z> Ziemowit Laski wrote: > I wouldn't mind COLLABORATING with someone on this (I don't think I > have sufficient cycles left in my day to go it alone). But first > and foremost, I'd like to have some sort of a statement from the SC > specifying the technical parameters of an acceptable solution -- > in other words, a guarantee that if a solution meeting those > criteria is created, it will be accepted. Generally the SC defers to the maintainers, especially the more experienced/senior maintainers - some of whom are SC members. In any case I don't think either the SC or the experienced maintainers can make much of a statement "specifying the technical parameters of an acceptable solution", nor can we make any "guarantee that if a solution meeting those criteria is created, it will be accepted". Sorry. Instead, you will have to make a proposal on this mailing list, and achieve a more-or-less consensus that what you're proposing is sufficiently useful and implementable that it makes up for any extra maintainance or compile-time performance problems. > No more Pascal string work from me. :) :) My take on that was that Apple gave up just a little too easily on that, and that we were close to accepting the \p extension. At least I was leaning in favor of it. -- --Per Bothner per@bothner.com http://www.bothner.com/per/