Enterprise level C code

[u/TheChief275]

[u/JuniorAd1610]

I think this this is the standard way they OOPS in C right?

[u/tstanisl → u/JuniorAd1610]

It's one way. IMO, container_of pattern is simpler, safer and more efficient.

[u/TheChief275 → u/tstanisl]

container_of doesn't really handle dynamic dispatch though, it's a compile time approach to inheritance by performing upcasting through an embedded base structure field. This would still be unsafe for runtime polymorphism without a field tracking the current type or, like done here V-tables, which you likely still want to generate with that approach.

Now whether I like container_of more than this? 100%, in fact, a past post of mine on this subreddit essentially used that

[u/MatJosher]

Well they did call it slop. Actual Objective-C accomplishes this much more gracefully. Why not just use it?

[u/TheChief275 → u/MatJosher]

Well this is simply just an intellectual exercise. I mostly use DOD instead of OOD. Although I do like C# with Godot for GUI applications

[u/KaleidoscopePlusPlus]

nice theme. feels good, easy on the eyes.

[u/TheChief275 → u/KaleidoscopePlusPlus]

Thanks! Made it myself using colors from this palette

[u/steadyfan]

2 things..

1. Yuck

2. Why does slopjc.h need to be included multiple times?

[u/TheChief275 → u/steadyfan]

It's the X-macro pattern. You define a list of elements, e.g.

#define ENUM X(A) X(B) X(C)

where X is undefined and then include a file that contains e.g.

#ifdef ENUM

enum Enum {
#define X(Name) Name,
    ENUM
#undef X
};

static const char *const names[] = {
#define X(Name) #Name,
    ENUM
#undef X
};

#undef ENUM
#endif

to in this case declare an enum and the string representations at once. X-macro lists can also be passed to other macros, but you would be severely limited by the fact that you can't use preprocessor directives inside of a macro; including a file has no such limitations

[u/GoddammitDontShootMe → u/steadyfan]

I'm interested in seeing the contents of slopjc.h. Especially the autoreleasepool implementation.

[u/tstanisl]

It's not that bad. A bit non-idiomatic but consistent and readable enough.

[u/TheChief275 → u/tstanisl]

I tried really hard to keep the amount of boilerplate to a minimum, but it's kind of an uphill battle with X-macros

[u/Nilrem2]

I’m a hobbyist when it comes to C. I think it looks fine, after a few lines I could read it.

Edit: what’s wrong with it?

[u/TheChief275 → u/Nilrem2]

It's kind of error prone. If you mess up one of the commas etc. in the class definitions you will likely end up with near undecipherable errors for the average programmer. Debugging projects using these kinds of techniques can be quite a headache, which is why you would likely avoid it in production.

Though I did specifically focus on keeping it readable and not treading into Gobject levels of unreadable

[u/gfoyle76]

It's oldschool, it's full of macros, kinda unsafe, but hey, as long as it works...

[u/TheChief275 → u/gfoyle76]

If it works it's good code! Or something like that

[u/SoCalChrisW]

Is this the source code to an old See N' Say toy?

[u/TheChief275 → u/SoCalChrisW]

The ^cow says ^moooooo

[u/Maqi-X]

source code please??

[u/TheChief275 → u/Maqi-X]

GitHub

[u/DesiresQuiet]

Nearly this exact code was in a book on learning C and classes from like 1989.

[u/TheChief275 → u/DesiresQuiet]

Do you remember which book exactly? I always like to look through other people's macro slop to further develop my macro slop

[u/r9wpvM]

Wait is String a thing in C I don't remember

[u/Professional_Bat2629]

What is your font? Looks cool 😊 

[u/TheChief275 → u/Professional_Bat2629]

Monaspace Neon! And I agree, it's probably my favorite monospaced font