This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: GCC 3.0 Release Criteria

To: Chip Salzenberg <chip at valinux dot com>
Subject: Re: GCC 3.0 Release Criteria
From: Richard Henderson <rth at cygnus dot com>
Date: Thu, 27 Apr 2000 23:02:39 -0700
Cc: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, mark at codesourcery dot com, gcc at gcc dot gnu dot org, geoffk at cygnus dot com, libc-hacker at sourceware dot cygnus dot com
References: <200004271445.KAA13474@caip.rutgers.edu> <20000427095256.C11838@cygnus.com> <20000427173305.J570@perlsupport.com> <20000427174246.C12403@cygnus.com> <20000427184257.M570@perlsupport.com>

On Thu, Apr 27, 2000 at 06:42:57PM -0700, Chip Salzenberg wrote:
> Is this a serious question?  Surely you can't make a serious plan
> that depends on never having to make an incompatible change?!

Of course it's a serious question.  It all depends on what
you mean by "incompatible change". 

If it means "user visible bug fix", no I don't expect never
to have to make such a thing.  If it means "change an interface
without providing a different function name" then, no, I don't
expect to have to make such a change.

r~

Follow-Ups:
- Re: GCC 3.0 Release Criteria
  - From: Chip Salzenberg

References:
- Re: GCC 3.0 Release Criteria
  - From: Kaveh R. Ghazi
- Re: GCC 3.0 Release Criteria
  - From: Richard Henderson
- Re: GCC 3.0 Release Criteria
  - From: Chip Salzenberg
- Re: GCC 3.0 Release Criteria
  - From: Richard Henderson
- Re: GCC 3.0 Release Criteria
  - From: Chip Salzenberg

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]