Re: API documentation

Funny, I learned that from IBM. Their response to a particular problem was
"we'll put that in the next version of the manual".

Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax

----- Original Message -----
From: <Terry.Rhoades@blum.com>
To: <RPG400-L@midrange.com>
Sent: Tuesday, February 06, 2001 10:25 AM
Subject: Re: API documentation


>
> And one lesson I learned from M$ is .... "it's not a bug, it's a
undocumented feature!"  <G>
>
>
>
>
>
>                     "oludare"
>                     <oludare@ix.netco        To:
<RPG400-L@midrange.com>
>                     m.com>                   cc:
>                     Sent by:                 Subject:     Re: API
documentation
>                     owner-rpg400-l@mi
>                     drange.com
>
>
>                     02/06/01 12:57 PM
>                     Please respond to
>                     RPG400-L
>
>
>
>
>
> One lesson that I learned from a professor is that even if you don't make
> mistake you can never code a "PERFECT PROGRAM".  At some point, if not
> earlier, your program will ABEND.  Lesson is "You can not program for all
> data, compiler and user mishaps"
>
> Oludare
>
> ----- Original Message -----
> From: "Buck Calabro" <buck.calabro@aptissoftware.com>
> To: <RPG400-L@midrange.com>
> Sent: Tuesday, February 06, 2001 12:19 PM
> Subject: RE: API documentation
>
>
> > The best programmers admit they made a mistake.  All programmers make
> them;
> > many simply don't admit it.  I believe that this statement is on-topic
and
> > on-thread.
> >
> > Buck
> > "Nothing is so firmly believed as
> >  that which we least know" -- Michel Montaigne
> >
> > > -----Original Message-----
> > > From: rob@dekko.com
> > > Sent: Tuesday, February 06, 2001 11:47 AM
> > > To: RPG400-L@midrange.com
> > > Subject: Re: API documentation
> > >
> > >
> > > Turns out it was my problem.  I was confused in this error code and
had
> my
> > > bytes provided and bytes available crossed.  My apologies to IBM.
> > >
> > > Rob Berendt
> > +---
> > | 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
> > +---
>
> +---
> | 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
> +---
>
>
>
>
> +---
> | 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
> +---

+---
| 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
+---