ever thought of going the depreciation route.
Something like what microsoft do with vc.
I.e. give a warning for depreciated constructs. With a hint as to how to
do it better?
Am 08.04.2012 21:30, schrieb Chet Ramey:
On 4/8/12 3:02 PM, Maarten Billemont wrote:
Any particular reason for not removing old undocumented functionality, or is
that mostly the nature of this beast - dragging along and maintaining ancient
code for the sake of compatibility?=
Because, as Linda discovered, there is still working code out there using
it. Maybe we'll get to a point where it's all gone, but we're not there
yet.
