Code Review? Looking for some thoughts on OOP C Code

I'm wondering if anyone would be so kind as to read some code I wrote, and provide feedback about things I may have done wrong. Maybe performance considerations? Things like that. And I'm wondering if anyone has implemented C libraries like this.

I've been writing some code that started as me experimenting with C, and ended up being quite useful. I haven't added thread safety yet, but will probably do that in the next week or so. The code was experiments on how to implement retain, release, copying, types, and deallocators. Essentially allowing anyone to implement a certain structure to gain most of this functionality. It was essentially my tests at writing some OOP C code.

I'm asking for this help because I don't work with or know anyone that writes C code, so I don't have a good outlet for some review. I'd even be ok making contact outside of this forum for back and forth.

The project is here:

beheadedmyway's oop_gd_c at master - GitHub

I would start by looking at the gd_obj* files, and then look at the gd_data* files to see how you'd implement the GD functions.

Thanks!

So I'm going to go out on a limb and say you've read the object-oriented C book. If you haven't it might prove an invaluable resource for a project like this.
Actually when I started out with C and wanted to move to C++ I learned most of the OOP concepts by learning how an OO system is implemented, and I have to admit it worked very well for me.

As for your code, I didn't look at much but I liked what I saw. It was clean and concise and there were debugging statements. I don't know about performance but I think in a case like this it might be better just to stick with short, clean code since the performance geeks are going to flock to C++ regardless.

Thanks for that link, I haven't read that one yet, it's next! That looks like an invaluable read.

I actually came the reverse direction, OOP first, then trying to wrap my head around C. I finally got c, so that code was just me experimenting with trying to figure out how you can be more productive with some of the bare minimum things I think should always be simplified.

You don't know by any chance where you can get the files that are associated with that book?

Quote:

---

Originally Posted by beheadedmyway

You don't know by any chance where you can get the files that are associated with that book?

---

The author of the document has his own webpage at RIT. You can find the download you need on this page. Or you can just click this for a download of the tar.gz file.

Thanks