Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!cica!ctrsol!ginosko!uunet!cs.utexas.edu!usc!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!hacgate!ashtate!dbase!awd
From: awd@dbase.UUCP (Alastair Dallas)
Newsgroups: comp.sys.mac.programmer
Subject: Re: CommToolbox & LSC
Summary: Use #defines
Message-ID: <197@dbase.UUCP>
Date: 14 Aug 89 16:53:27 GMT
References: <10011@bsu-cs.bsu.edu> <2419@husc6.harvard.edu>
Organization: Ashton Tate Devlopment Center Glendale, Calif.
Lines: 24

In article <2419@husc6.harvard.edu>, siegel@endor.harvard.edu (Rich Siegel):
> In article <10011@bsu-cs.bsu.edu> mithomas@bsu-cs.bsu.edu (Michael Niehaus):
> 
> >prototypes.  LSC doesn't seem to like this.  I removed the "const".  Will 
> >this work?
> 
> 	"const" is an ANSI-ism not supported by THINK C.

THINK C thoughtfully provides a predefined symbol, "THINK_C," so that you
can write a simple header file:

#ifdef THINK_C
#define const
#define volatile
#define class struct
#endif

and this way pretty much get around any slight incompatibilities.  In case
you're not aware, 'const' brings very little to party.  The compiler is
supposed to check to make sure you do what you said you'd do and not let
you write to a const object.  (C Chauvinist Pig voice:) If you want that
kind of hand-holding, boy, better code in Pascal.

/alastair/