× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Calling for API interface examples (Was: QWCRSVAL API)
  • From: Colin Williams <Williamsc@xxxxxxxxxxxxxxxxx>
  • Date: Fri, 29 Oct 1999 15:11:49 +0100

What about allowing people to send you a single source member that uses
a particular API. 

I have a program that dumps the first 32K of a dataqueue
to  a file, parameters are data queue and entry length.

>-----Original Message-----
>From: Henrik Krebs [mailto:hkrebs@hkrebs.dk]
>Sent: Friday, October 29, 1999 12:04 PM
>To: MIDRANGE-L@midrange.com
>Subject: Calling for API interface examples (Was: QWCRSVAL API)
>
>
>NEVER EVER POST GOOD IDEAS TO THIS LIST!
>
>Why not? Here is an example of how it just creates more work for YOU:
>
>The "QWCRSVAL API" tread had a few entries about "Is 
>API-interfacing easy or not", so I sugested to make a 
>collection of such
>interfaces. This was welcomed, so I had to do it (more work!).
>
>However the collection is ment as a place where YOU contribute 
>with YOUR examples. Ladies and Gentlemen: The time is up now to post
>your examples to me. I'll then put them on the air at 
>http://hkrebs.dk/apiinterfaces.html.
>
>The examples should be sent to 
>mailto:apiinterfaces@hkrebs.dk?Subject=API-interface as 
>attached zip-files following this scheme:
> o  Placed in the Public Domain with no restrictions at all. 
> o  Packed in a PC .ZIP-file, source only. 
> o  Simple stand alone programs, ready to compile, test and 
>modify. Subroutines are supplemented by a small main routine that sets
>up the parameters etc. 
> o  Authors name and @ddress included if he accepts questions 
>about the interface. 
> o  Restrictions and prerequisites described in the program 
>source. No need for any additional user guides. 
>
>For those of you who just want to improve your own collection: 
>Don't go there yet. There is only one single interface at the
>moment. But hopefully in a few weeks.
>
>Regards
> 
>Henrik
>http://hkrebs.dk
>
>
>----------
>Fra: Wayne Capwell <wayne@redoaktech.com>
>Til: MIDRANGE-L@midrange.com
>Emne: Re: Sv: QWCRSVAL API
>Dato: 28. oktober 1999 13:27
>
>I'd like to see a collection.  I can't contribute much yet, but with a
>few examples to get started, I'm sure I can offer something.
>
>Henrik Krebs wrote:
>> 
>> API's
>> 
>> Difficult?
>> Piece of cake (or "Baby's food" as we say in Danish)?
>> 
>> Anybody think it's a good idea to publish a collection of 
>API-calls (e.g. in RPG/400 plus ILE RPG and maybe plus CLP)? If so,
>I'll
>> willingly host it.
>> 
>> Send your reply to this list (including any offer to 
>contribute, but do not post tons of code yet). If there is a 
>common need,
>I'll
>> try to set up a scheme and call for contributions to such a 
>library in the public domain).
>
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
>| To unsubscribe from this list send email to 
>MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator: 
>david@midrange.com
>+---
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.