| >Thanks for the come back. Can you say what is the minimimum mpw C stuff I
| >should buy to do the above. Also I might mention that the C code I hope
| >to integrate is in ANSI C.
|
| I know very little about developing C on the Macintosh. I used Think C
| two or three years ago to do a small project, and have used MPW a little
| bit to assemble MCL's kernel, but that is the extent of my experience.
| >From looking at the November, 1992 APDA catalog, I would guess that you would
| need to get the MPW C Bundle, which was listed for $425. The description of
| the MPW C compiler version 3.2.4 says "The MPW C compiler supports K&R C,
| as well as many ANSI extensions to C, including function prototypes and strong type checking. It includes a standard C library that offers the functions
| described in the ANSI C standard." I do not know if "many ANSI extensions"
| means that it will have problems with your "ANSI C", nor do I know if
| Think C is closer to the ANSI standard (or if that will matter for your
| code), or how the effort involved in building Think C stubs using Guillaume
| Cartier's package compares to writing DEFFCFUN stubs to interface to MPW C.
|
| Can someone else help out?
--->
My Think C interface was originaly created so I could write the floating
point routines of my 3D viewing package in C (MCL's compiler doesn't
recognize floating point declarations and so generates inneficient code
relative to both speed and memory allocation) (note that this is not a
problem anymore since we now have Erann Gat's wonderful FPC package).
With that in mind, my interface was thought out for fast development
(changing your C code, compiling the resource, testing it in MCL, etc...).
On the other hand, using it to interface a big package of C code already
writen is more complex. The biggest problem is that my interface doesn't
understand everything type a C routine can pass or be passed. For instance,
if you want to pass a structure via a pointer, no problem; but if you
want to pass the structure itself... that is not done.
Hope this clarifies things a bit,
Guillaume.
PS: If you have more specific question about my Think C interface,
