Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!seismo!esosun!ucsdhub!jack!man!crash!billk
From: billk@crash.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Calling CINIT from LATTICE-C and/or MANX/Atztec-C
Message-ID: <844@crash.CTS.COM>
Date: Thu, 26-Feb-87 00:21:45 EST
Article-I.D.: crash.844
Posted: Thu Feb 26 00:21:45 1987
Date-Received: Sat, 28-Feb-87 01:50:52 EST
Sender: root@crash.CTS.COM
Organization: People-Net [pnet01]
Lines: 42

dillon@CORY.BERKELEY.EDU (Matt Dillon) wrote:

>       I think it's a macro. ... probably #defined'd in one of the 
>graphics include files...

I don't know anything about C compilers (though I can *read* C pretty well...)
but CINIT is a routine in the graphics.library.

Gee.  It *is* a macro.  According to appendix A p. 105 of the RKM, here's what
CINIT does:

NAME
        CINIT  -- initialize user copperlist to accept intermediate
        user copper instructions

SYNOPSIS
 struct CopperList  *CINIT( c , n )

FUNCTION
        allocates/initializes copperlist datastructures/buffers

INPUTS
        c  = pointer to UCopList structure
        n  = number of instructions buffer must hold

RESULTS
        this is actually a macro that calls UCopperListInit(c,n)
        If (c=0) allocate CopperList structure and a buffer
        to hold n copper instructions.  If (c != 0) then
        just reinitialize the list to accept copper instructions
        and ignore n.

BUGS

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Well, that may or may not be useful information... Hopefully the former.

Bill Kelly      {akgua, hplabs!hp-sdd, sdcsvax}!crash!pnet01!billk

"An apple a day keeps the doctor away, especially if aimed well."

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~