Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!srcsip!tcnet!pwcs!stag!root
From: stag!thelake!steve@bungia.mn.org (Steve Yelvington)
Newsgroups: comp.sys.atari.st
Subject: Re: Sozobon C
Message-ID: <1989Jul29.203916.29778@stag.UUCP>
Date: 29 Jul 89 20:39:16 GMT
Sender: root@stag.UUCP (Computer Abuser)
Organization: Mindtools ST Access Group
Lines: 67


 stevens@prlhp1.prl.philips.co.uk (Francis Stevens) writes...
>
>I have a 520ST and have recently been given a copy of the Sozobon C compiler,
>so far I have been using this with some success to write some small C programs.
>One thing that didn't come with the disk (or on it) was any form of 
>documentation for the compiler etc.. (OK I know it was free, so what do I 
>expect)  But just on the off chance.... is there any one out there who knows
>of any such documentation (even if it's just the name of a book I need to buy)

There are 20 pages of documentation on the compiler and utilities. The
library (dLibs, by Dale Schumacher) is very well-documented separately --
30 pages or so, I think. And, of course, SOURCE CODE for everything is
published.

The whole shebang is available on the panarthea file server, or from:

Tony Andrews
5902E Gunbarrel Av.
Boulder, CO 80301 USA

I think he wants $10 (bargain of the century) for making disk copies and
mailing it to you. For a non-USA address, you probably should add
international postage.

In the meantime, you can use any good modern C reference book -- dLibs is
very complete. Do not, however, try to use ANSI-style function prototypes.

>or if anyone has any usefull information about the compiler (like is it 
>possible to compile a program on another (RAM) disk ?) 
>I would be grateful for the info.

Sure.

If you run cc with no args, it will give you an explanation.

cc -O -o d:\fubar.tos c:\fubar.c b:\neatstuf.s a:\morestuf.o
    ^  ^     ^            ^            ^            ^
    |  |     |            |            |            |
    |  _______           c source      |          object file on drive a:
    | output this        on          asm file on drive b:
    | program on         drive c:
    | drive d:
    |
   run the
   optimizer
 
Note: hcc.ttp (the preprocessor-parser-code generator) writes totally
bass-ackwards assembler code and expects you to run top.ttp to optimize
it. The only time I do not run the optimizer is when I'm messing round
with line A (illegal opcodes), which choke the optimizer. I recompiled cc.c
to force the -O switch to be TRUE even when I forget to type it.

If you're using a RAM disk, it's best to put the compiler and/or libraries
there, using the PATH and LIB environment variables to point to them, and
keep your C code and output program on real media. If your test program
crashes the system, you really don't want to lose the work you've done.

Since the original release of Sozobon, a couple of useful third-party
add-ons have surfaced: Ian Lepore's GEMFAST bindings (two libraries,
AESFAST.A and VDIFAST.A), and David Brooks' FPLIB replacement
floating-point mathematics library. They also are on the panarthea file
server.


  -- Steve Yelvington, up at the lake in Minnesota
  ... pwcs.stpaul.gov!stag!thelake!steve