On Tue, Oct 25, 2005 at 04:05:55PM -0700, Stan Shebs wrote:
> I think you've managed to get everything backwards. We have potential
> customers (dunno if I'm allowed to name them, so I won't) who can't
> use GCC because of its current behavior.
I had thought that a numer of users had requested the current
behavior back in the egcs days, though I can't track down the brain cell I
stored that info in; also, I'm having a hard time picturing source code that
a) exhibits different behavior because of this bug, and
b) is maintainable (remember, the behavior depends on the presence
of characters that are completely invisible to many tools).
Perhaps you could explain (without violating the customer's
confidentiality) how it is that this is an important problem?
> minute to make them happy, but of course then we'll have to tell them
> "don't use FSF GCC, you'll lose". So we're offering to make FSF GCC
> work for these users also, and asking for input on the idea. As
> always, it's the community's choice as to whether this is a desirable
> feature for FSF GCC, and that's part of the discussion, but at least
> don't p*ss on us for making the offer in the first place!
I think that there was only pissing because this feature that many
considered useful was labeled a regression and a bug.
