Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Small C code (was: Portable "C" Code)
Message-ID: <8704032000.AA28584@cory.Berkeley.EDU>
Date: Fri, 3-Apr-87 15:00:03 EST
Article-I.D.: cory.8704032000.AA28584
Posted: Fri Apr  3 15:00:03 1987
Date-Received: Sun, 5-Apr-87 05:54:16 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 41

>What peeves me is that the NODEBUG option for BLINK wasn't documented.
>I've got a paper by the Software Distillery people describing how to
>get small binaries out of Lattice. That's where I found out about
>NODEBUG. Applying most of the rest of it would break mg's portability
>to other things.
>
>BTW, Matt, exactly what makes writing software for both compilers so
>inherently ineffecient? Mg doesn't have much problems with that,
>though trying to stay portable to BSD Unix (first among many others)
>causes problems.
>
>	Thanx,
>	<mike

	Well, actually, ND is documented when you give Blink with no 
arguments (or was it with '?'.. forgot).

	'standard' C programs aren't difficult write for both compilers, but
when you get into other things, like my MWB, which require assembly language,
it gets quite different.  For instance, I have to specify the large code and
data model using the FAR and NEAR operations in the assembly, which is
incompatible with the C-A assembler.

	As far as the compiler goes, with 2Meg of RAM I have it entirely in
VD0: (thanks Perry!), and have cc aliased to 'cc +L +Ivd0:clib/symbols'...
that is, I've pre-compiled all the symbols in every Amiga include file that
exists.  Needless to say I can still put #include statements in the source
without loosing efficency, but I have on way of knowing if I forgot any
#includes since I get all the symbols whether I have them or not.

	So the problem is more trying to explain the enviroment to 
people than actually coding changes.  But you can see the trouble someone
might have to go through to get Aztec code to compile with Lattice...
Adding #include files, modifying assembly language, taking out dependances
on certain Aztec library functions (though I personally do not usually use
those functions), differences with floating point.  I hesitate to 
distribute source because I *know* I'm going to get dozens of letters from
people trying to compile it.


				-Matt