On Feb 18 13:53, Howland Craig D (Craig) wrote:
I see two possible approaches to take with respect to this problem:
1) Remove the functions (until adequate replacements can be found).
2) Point out their shortcomings in the documentation and recommend
that they not be used.
[...]
Personally, I prefer the first approach.
That's not possible. You would break backward shared lib compatibility
with already exsisting applications.
So finally to the approach question: should the functions be
removed, or should they be kept with the BUG being documented?
Better document it.