--------------------------<snip>--------------------
Is it just me, or does anyone else have the understanding that an
interface needs written documentation?
Example: If you are using some of the Unix Systems Services, or TCP/IP,
you are told to look in the macro library for doc.
It seems to me that if a system service is documented (say a BPXnccc
call), then all the info for this should be given and not send one off
to read the code of some macro.
Any thoughts?
------------------------<unsnip>------------------------
Steve, I agree with the concept. Unfortunately, the folks who write the
manuals aren't always as technically oriented as the folks that define
the interfaces. So sometimes things slip through the cracks or are "lost
in translation". But the macros are usually written by the techie-types
that designed and implemented the various interfaces; and the techies
tend to have a much stronger interest in accuracy and completeness.
----------------------------------------------------------------------
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
