Re: Wrapping a C function library (as source) in an ObjC class...

2010-03-28 Thread Jens Alfke
On Mar 28, 2010, at 9:32 AM, Clark Cox wrote: >> When importing header files into my >> implementation file ".m", do I #include them or #import them? How about >> existing library headers (like )? > > You can do either. To be precise: #import is just like #include, except that the second #impor

Re: Wrapping a C function library (as source) in an ObjC class...

2010-03-28 Thread Clark Cox
On Sun, Mar 28, 2010 at 9:18 AM, William Squires wrote: > ... and other things. > > 1) I have a C library (as a .c and .h) file. I want to encapsulate this > functionality in an ObjC class. When importing header files into my > implementation file ".m", do I #include them or #import them? How abou

Wrapping a C function library (as source) in an ObjC class...

2010-03-28 Thread William Squires
... and other things. 1) I have a C library (as a .c and .h) file. I want to encapsulate this functionality in an ObjC class. When importing header files into my implementation file ".m", do I #include them or #import them? How about existing library headers (like )? 2) If my C code uses