TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
In my experience, this is a common and widely-understood term among software
engineers. So, unless you're targeting your checklist of APIs to a
non-engineer audience, I would stick with this term. I know that doesn't
answer your question. So, you might want to go with "no longer supported" or
"obsolescent" or "extinct" or "defunct". DB.
deprecated
Said of a program or feature that is considered obsolescent and in the
process of being phased out, usually in favour of a specified replacement.
Deprecated features can, unfortunately, linger on for many years. This term
appears with distressing frequency in standards documents when the
committees writing the documents realise that large amounts of extant (and
presumably happily working) code depend on the feature(s) that have passed
out of favour.
> -----Original Message-----
> From: Stern, Geoff [mailto:GStern -at- NetSilicon -dot- com]
> Sent: 10 October 2001 15:06
> To: TECHWR-L
> Subject: Terminology question: Deprecated function
>
>
> De-lurking to pose a terminology question:
>
> Our software engineers have been using the term "deprecated
> function" to mean a function that has been (and still is)
> fully supported but will not be supported in some future
> version (usually the next one or so).
>
> None of us -- engineers or writers -- likes this term,
> although it seems to be widespread usage in API documentation.
>
> Any suggestions for an alternative that's fairly laconic? (It
> would be nice to have something short enough to use in a kind
> of overview table or checklist of APIs.)
>
> Thanks.
>
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Announcing new options for IPCC 01, October 24-27 in Santa Fe.
Attend the entire event, select a single day, or sign up for
a Saturday postconference workshop. http://ieeepcs.org/2001
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
