[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#25890: Default value of digits-per-component?

From: Clément Pit-Claudel
Subject: bug#25890: Default value of digits-per-component?
Date: Wed, 29 Mar 2017 23:10:07 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0

On 2017-03-29 22:36, Eli Zaretskii wrote:
>> Cc: Eli Zaretskii <address@hidden>
>> From: Clément Pit-Claudel <address@hidden>
>> Date: Wed, 29 Mar 2017 16:01:09 -0400
>>> If the change I made is nevertheless deemed too drastic, then what are
>>> our alternatives?  The only one I could think of is to define a new
>>> function and deprecate color-name-to-rgb in favor of that new
>>> function, which will then display warnings when code using it is
>>> compiled, and eventually cause them to make changes in their code
>>> anyway.  Is that better?  Or are there any better ideas?
>> It sounds much better to me: the current solution breaks all code silently
> I'm not sure I understand how come all users of that function are
> suddenly broken.  A different result doesn't yet mean breakage, unless
> the caller actually expected the precise format the old version was
> producing, and relied on that.  Is that indeed so in the callers you
> saw?

For me, yes, definitely: I was producing HTML webpages with inline CSS and 
LaTeX documents.  Both of these got very confused when they started receiving a 
longer hex codes :)
I don't know about the uses on GitHub. 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]