On 8/29/25 12:32 PM, Connor Wilkins wrote:

In theory, since it's never been documented, I could flip the define in 
config-top.h and disable it by default.

This assumption is the root of the problem.
If it's not documented, then as far as some ordinary users are concerned, it is NOT 
deprecated. "The user is wrong" is not an acceptable response to an inadequacy 
of documentation.

I tend to agree with this... If you're not communicating the fact that
a feature is deprecated then how is a typical user to know that?

If a feature is never documented or officially announced (e.g., in NEWS,
or in a release announcement), why would a typical user assume it's
available at all?

I personally think that's an absurd notion. Features deprecated on release?
Why would you think the feature is available when it's not documented or
announced?


--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    c...@case.edu    http://tiswww.cwru.edu/~chet/

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to