This is the mail archive of the gcc-patches@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]
Other format: [Raw text]

Re: PATCH RFC: Proposed patch for PR c++/7874


On Sep 7, 2005, at 5:43 PM, Gabriel Dos Reis wrote:
Obviously, other people also use the compiler in ways that actually do
matter to them.

I misled you into misreading what I was trying to say, sorry. By it, I meant the ability to compile code that is invalid but `works' for them without using an older compiler. It would have been more clear if I had said, apparently I'm one of the few people with users that actually use the compiler in ways in which the ability to compile incorrect code that used to compile for them actually is important to them, but, even that misses the central concept of what we are talking about. Essentially, the ability for them to be able to report problems, for me to fix those problems and deliver a newer compiler that also happens to include a merge in from the same release branch as I started with, without totally hosing them. They can rewrite their code, but they would rather ship their app, with the newer compiler, to pick up the bug fixes they require, but, they don't want to take the time to market hit. In essence, you want to force them to take the time to market hit, sooner. I want to only hit them in a x.y.0 release, once a year, they can then use x.y-1.z until such time as they port up to x.y.0, but, once they do this, I want to stop molesting them as much as possible with x.y.n+1 releases.



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