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.
Sorry, but it's pretty standard in the industry. The first
I encountered it was in the world of U.S. federal programming
language standards. The COBOL standard for 1974 included certain
functionalities that were replaced by others in, say, the 1985
standard. At that time, the 1985 standard described the old
functionalities as "deprecated" and this meant that, though they
were still supposed to be available in COBOL implementations that
claimed standards conformance, they should not be used because
the next standard was expected not to include them.
--Guy K. Haas gkhaas -at- usa -dot- net
Software Exegete in Silicon Valley
-----Original Message-----
From: Stern, Geoff [mailto:GStern -at- NetSilicon -dot- com]
Sent: Wednesday, October 10, 2001 7:06 AM
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?
Thanks.
==
Geoff Stern
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.