David Alcock wrote:
In the Java world, there is a term called "deprecated" for older
API calls that still work but newer replacement ones are
available. Here's one explanation:
http://www.mindprod.com/jgloss/deprecated.html
This term has been used for quite some time in the mainframe world
(possibly for an even longer time than Java has been a language). Search
the z/OS collection for the word "deprecated". I found hits in 40 books.
It'd be nice if IBM added a comment or MNOTE when an older macro
like STAE is expanded. The comment would have a standard format
which could be searched on in listings. The code generated
would not be changed, just an additional comment printed.
Or they could do something like what's being done in MCSOPER for z/OS
V1R7 when certain obsolete keywords are used. The macro generates a
severity one MNOTE, but provides a mechanism to suppress it for those
cases in which you know its OK to use them (e.g., code that is
guaranteed to execute on a back release only).
Problem is, nobody wants to touch the "old" stuff. Doing so requires
(albeit minimal) development time, testing time, and documentation
effort -- all of which take away from resources allocated for "new"
functionality. If it ain't broke, don't fix it -- *especially* if
nobody's paying for it to be fixed!
--
.-----------------------------------------------------------------.
| Edward E. Jaffe | |
| Mgr, Research & Development | [EMAIL PROTECTED] |
| Phoenix Software International | Tel: (310) 338-0400 x318 |
| 5200 W Century Blvd, Suite 800 | Fax: (310) 338-0801 |
| Los Angeles, CA 90045 | http://www.phoenixsoftware.com |
'-----------------------------------------------------------------'
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
