On 02/19/2010 09:39:40 PM, Karl O. Pinc wrote:
> If someone who explicitly chooses a functionality
> needs to get a warning about the default they
> should get this warning at ./configure time --
> the time they make the choice.
The only time I can think of that a warning should
be delivered to those who explicitly choose
functionality in the process of deprecation
is to, _after_ the default has changed,
deliver a ./configure time warning to those
who explicitly choose the default telling them
that they no longer have to be explicit because
they are choosing what is now the default.
It hardly seems worth it.
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
