Re: api documentation was RE: SYSTEM prototype?

Personally, I have no trouble with the API documentation.  That said, it
took a while to get the hang of the manuals.  I can usually look up an API,
prototype it in RPG, and write code that uses it without a problem, first
time through.

The API documentation doesn't provide information about how to use it in
RPG.  There are a few things you need to find out for yourself, either by
trial and error or exhaustive searching of the documentation.  After that,
calling APIs becomes second nature.

To be honest, the above sounds to me like a summary of the process of
learning any new programming technique.

--
Paul

----- Original Message -----
From: "Joel Fritz" <JFritz@sharperimage.com>
To: <RPG400-L@midrange.com>
Sent: Wednesday, January 31, 2001 4:00 PM
Subject: api documentation was RE: SYSTEM prototype?


> I've followed this thread quietly, and while people who've responded have
> answered the particular question about system() and the more general
> question about the location of api documentation, it seems to me that the
> word "easily" is the key.  Raise your hand if you think the api
> documentation is easy to find and provides much information on how to use
> the apis in RPG. <g> (CEE apis excepted.)


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---