HP-UX 11i Version 1.5 Release Notes, September 2001

Programming
Obsolescence and Deprecation of APIs
Chapter 7120
• the specification is in flux
• less value to users
• functionality no longer makes sense
• functionality has been replaced
• support/enhancement expectations have been lowered
• usage is discouraged
• warnings against usage/alternatives are provided
• the provider continues to test functionality
• migration plan/tools are provided
The reasons for marking an interface as “deprecated” may include:
•marked "to be withdrawn" by standards
• support is available via more standard means
• equivalent, enhanced, more reliable counterparts exist
• also all reasons listed in the "Obsolete" section below
Obsolete: An "obsolete" interface may have the following characteristics:
• functionality is no longer available on the system
• runtime support is undefined
• cannot develop or build with this interface
• documentation is not provided or recommends against usage
• the final stage of the product life cycle has been reached
The reasons for marking an interface as "obsolete" may include:
• underlying infrastructure in either the software or hardware is
obsolete or not available
• changes to the system have decreased reliability
• miscellaneous business decisions such as:
— third parties solution exists
— not strategic
— support costs are too high