On 8/27/25 12:22 PM, Connor Wilkins wrote:
On 8/27/25 11:32 AM, Chet Ramey wrote:
On 8/27/25 11:22 AM, Connor Wilkins wrote:
I'm of the opinion that if there is a supported feature with no plans for
deprecation
or removal, it should be documented. Even if it's not widely used, it's still
supported
with (as you said) no plans for removal.
What does deprecation look like to you? How should bash indicate that
state, and where should it do so?
Typically deprecation warnings happen in the documentation.
Something to the effect of:
<feature>
DEPRECATED. Prefer <alternative>. Will be removed in <version>.
This has never been documented.
In theory, since it's never been documented, I could flip the define in
config-top.h and disable it by default. I thought about doing that for
bash-5.2, but did not.
--
``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/
