Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!bu.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!dev8j.mdcbbs.com!astor
From: astor@dev8j.mdcbbs.com
Newsgroups: comp.sys.mac.comm
Subject: Re: ? Using the Comm. Toolbox with THINK C ?@
Message-ID: <1990Aug9.100703.1@dev8j.mdcbbs.com>
Date: 9 Aug 90 10:07:03 GMT
References: <1990Aug2.112522.1@dev8j.mdcbbs.com>
Organization: McDonnell Douglas M&E, Cypress CA
Lines: 28

> ...
> Has anyone programmed an application for the Communications Toolbox
> using THINK C?  If so, what did you do for any include files and
> definitions of the CTB traps?  Anything else I should know?
> ...

Thanks to the many people who responded to the above request.  It
is indeed possible to use the Communications Toolbox with THINK C.

To start with, you need to convert the CommToolBox.o file supplied
with CTB to a THINK C project using the oConv utility provided
with THINK C.  You also need to use a .v file to get the right
case sensitivity for the converted project.

Next, you can either edit the supplied include files, removing the
// style comments, the const parameters, and a few other things, or
if you have access to the developer CD series, you can take:
	CommResources.h, Connections.h, CRMSerialDevices.h
	CTBUtilities.h, FileTransfers.h, and Terminals.h
from the THINK C Interfaces folder.

So far, everthing is working like a charm.
-- 
  ===============================================================
 |    Andy Astor            |   Voice:     (714) 952-5836        |
 |    McDonnell Douglas M&E |   UUCP:     uunet!mdcbbs!astor     |
 |    Cypress, CA  90630    |   Internet: astor@mdcbbs.com       |
  ===============================================================