{"id":55,"date":"2010-07-22T14:38:00","date_gmt":"2010-07-22T12:38:00","guid":{"rendered":"https:\/\/daniel.liljeberg.io\/?p=55"},"modified":"2021-01-29T12:40:31","modified_gmt":"2021-01-29T11:40:31","slug":"object-oriented-development-in-ansi-c","status":"publish","type":"post","link":"https:\/\/daniel.liljeberg.io\/sv\/2010\/07\/22\/object-oriented-development-in-ansi-c\/","title":{"rendered":"Object Oriented development in ANSI C?"},"content":{"rendered":"

Even though I once started with, and for a long time developed with, procedural languages, over the years I have started to think much more object oriented when I develop. It started when I learned C ++ and has become an intuitive way for me to see systems and solutions to my development problems. A while ago, however, I found myself in the situation of being limited to ANSI C. The code was to be compiled on gcc and thus new<\/strong>, class <\/strong>and the like are just to be forgotten. Much of the code in place was written purely procedurally, but that part tried to encapsulate different parts by grouping them in different files and so on. It also clearly struggled with many of the large scale systems issues that C++ aimed to solve.<\/p>\n\n\n\n

I also found it surprisingly difficult to completely let go of the object-oriented way of thinking and grew interested in exploring to what degree many of the object oriented ideas could be used in plain ANSI C. This is the first the time I do this, so I learn and come up with new things all the time and a lot will probably be revised. But here are some thoughts.<\/p>\n\n\n\n

Inheritance<\/h2>\n\n\n\n

Inheritance can to some extent be faked by your structs looking identical on the parts they have in common and that all specific parts come last in the structure.<\/p>\n\n\n\n

struct foo {\n  int a;\n  int b;\n}\n\nstruct bar {\n  int a;\n  int b;\n  char* s;\n}\n\nvoid printStruct(struct foo* obj) {\n  fprintf (stderr, \"a:%s \\nb:%s \\n\", obj->a, obj->b);\n  return;\n}<\/pre>\n\n\n\n
printStruct <\/strong>will now be able to receive both foo <\/strong>and bar<\/strong> structs. But the downside is that you have to type your bar <\/strong>struct yourself if you want to submit it to the function. The function can also not print the string in a bar <\/strong>struct as it would be a problem if you had in fact sent a foo<\/strong> struct. One way to get around this is to let the function take a void*<\/strong> instead, but then you can really send it anything and it is impossible to know which struct you are really receiving. A “solution” may be to have a type of field in your struct. You can then let the function check what type it is and choose what it should do with the struct based on that.<\/p>\n\n\n\n
enum StructType {FOO, BAR};\n\nstruct foo {\n  structType type;\n  int a;\n  int b;\n}\n\nstruct bar {\n  structType type;\n  int a;\n  int b;\n  char* s;\n}\n\nvoid printStruct (void* obj) {\n  \/\/ Type throw to the \"lowest\" type and check the type field\n  switch (((foo*)obj)->type) {\n  case FOO:\n    fprintf (stderr, \"a:%s \\nb:%s \\n\", ((foo *)obj)->a, ((foo*)obj)->b);\n    break;\n  case BAR:\n    fprintf (stderr, \"a:%s \\nb:%s \\ns:%s \\n\", ((foo*)obj)->a, ((foo*)obj)->b, ((foo*)obj)->s);\n    break;\n  default:\n    fprintf (stderr, \"UNKOWN TYPE! \\n\");\n    break;\n  }\n\n  return;\n}<\/pre>\n\n\n\n
Now the function will print the string if it is a bar <\/strong>struct you submit. Of course, type must be set to the correct value, something that could be managed via “new”-functions that create the structs. For example<\/p>\n\n\n\n
struct foo* MyFoo = NewFoo(aVal, bval);<\/pre>\n\n\n\n
I have heard rumors that you should be able to define your struct in such a way that you could actually let the printStruct<\/strong> function take a pointer to the “base” struct, but this is not something I have succeeded with. If anyone knows, feel free to shout.<\/p>\n\n\n\n
Private variables<\/h2>\n\n\n\n
Normally in object oriented programming we end up having a lot of variables in our objects that we do not really want the end user to touch. In C++ we declare these as private <\/strong>(or protected<\/strong>). But in a struct in ANSI C, this possibility does not exist. However, what you can do is fake this to an extent. In you .h file you declare<\/strong> the struct with something like<\/p>\n\n\n\n
typedef struct MyObj MyObj;<\/pre>\n\n\n\n
and then in you .c file you write the actual definition<\/strong><\/p>\n\n\n\n
struct MyObj {\n  int a;\n  int b;\n}<\/pre>\n\n\n\n
Now all your functions in your .c file for the object will know what your struct looks like inside, but for everyone else who only has the declaration in your .h file to go on, the member variables will be “hidden”. We have now managed to recreate some of the possibilities with private variables. If you want a static private member variable, you achieve similar functionality by declaring it outside your struct in your .c file.<\/p>\n\n\n\n
Member functions<\/h2>\n\n\n\n
Member functions are a big part of object oriented programming. Let’s say you for instance, have an array of pointers to your objects, all of which can now be of a slightly different type. But we know that everyone should execute a “run”-function. However, not every object should do the exact same thing. Here we can do as before to check a type of variable in our struct and based on that choose what we are going to do. Something that is nicer, however, is to use member functions. Something that can be achieved with ANSI C.<\/p>\n\n\n\n
typedef int funcPtr ();\ntypedef struct myObj {\n  int a;\n  int b;\n  funcPtr* run;\n} myObj;\n\ntypedef struct myOtherObj {\n  int a;\n  int b;\n  funcPtr* run;\n  char* s;\n} myOtherObj;\n\nint runOne () {\n  return 1;\n}\n\nint runTwo () {\n  return 2;\n}<\/pre>\n\n\n\n
In your “new”-functions for the different “objects” you assign the functions.<\/p>\n\n\n\n
struct MyObj* NewMyObj (int aVal, int bVal) {\n  struct MyObj* this = (stuct MyObj*) malloc (sizeof (struct MyObj));\n  this->a   = aVal;\n  this->b   = bVal;\n  this->run = runOne;\n  return this;\n}<\/pre>\n\n\n\n
Then you can simply call the function on your “object”.<\/p>\n\n\n\n
struct MyObj* myObj = NewMyObj (10, 20);\nint result = myObj->run();<\/pre>\n\n\n\n
The result will now be 1<\/strong> when we assigned runOne<\/strong> to our “run”-function in the constructor and that function returns 1<\/strong>. If this object were part of an array of objects we could have looped them and run their respective “run”-functions and each of the objects could in turn point to completely different implementations of that function.<\/p>\n\n\n\n
These were just a few quick things I’ve come up with in recent days. Feel free to share tips and ideas. Please note that the code above has not been compiled there may be some small errors here and there, but the idea itself should be clear.<\/p>\n\t\t\t\n\n\n
\n
Comments<\/h3>\n
 \n
\n\t<\/a>\n\t
\n\t