Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uwm.edu!linac!att!ucbvax!FTP.COM!backman
From: backman@FTP.COM (Larry Backman)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: What's in FTP OS/2 Developer's Kit?
Message-ID: <9105201409.AA12919@ftp.com>
Date: 20 May 91 14:09:26 GMT
Article-I.D.: ftp.9105201409.AA12919
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 32


 >> 
 >> Has anyone used the PCTCP OS/2 Developer's Kit?  What's
 >> included? Is it essentially documentation, an include file, and
 >> def files for the kernal DLL's?
 >> 
The DevKit consists of an include tree, set of .LIB files,a set of DLL's,
and a tree full of sample programs.

All API's are in DLL's.  The TCP kernel is not a DLL but a device driver.
The DLL's are standalone, multi-threaded DLL's.

 
 >> Or does it use Microsoft-compatible libraries?  The latter has
 >> the disadvantage of being incompatible with other compilers,
 >> with the typical hard-wired library request records.
 >> 
As just mentioned; the interface is via DLL's.  The Socket API ( as well
as the port of the Dos NetLib, FTP, & TN libraries as DLL's) are all
_cdecl entry points to the DLL.  We originally were trying for Pascal style
enty points but the problems with MSC 6.0's errno variable forced us to
use cdecl's instead.

I'm interested in making sure that the DLL's work with environments other
than MSC C6.0.  What compiler are you using?





					Larry Backman
					backman@ftp.com