Yes sure.

Unfortunately e.g. ctl then ends up with something like:

…
struct _host {
  int status;
  str name;
};

typedef struct _host Host; // <-
…
deq_Host_push_back(&gizmo, (Host){301, str_init("joearms.github.io")})
+;
[download]

Instead of deq_host_push_back in case of lowercase.

Lowercase looks less perverted to me for the moment - but I am capable of learning.

First of all, that's not what I recommended. You still naming the type struct _host which makes no sense.

As for putting an uppercase "Host" in the middle of a function name, why would would do something silly like that. Or do you mean Host_push_back akin to Perl's Host::push_back? Definitely a gain since there's no equivalent to ::. Different things should look different.

And you didn't say what you'd use instead of Host host;. What would the following look like in your system?

Host host = Host_new();
[download]

”… why…do something silly like that”

It’s not me, the library works like this:

struct _host {
  int status;
  str name;
};

typedef struct _host host;

void host_free(host *);
host host_copy(host *);

#define T host // <- custom type
#include <deq.h>

// functions to implement
void host_free(host *h) { str_free(&h->name); }

host host_copy(host *h) {
  host _ = *h;
  _.name = str_copy(&h->name);
  return _;
}
[download]

The library then provides:

container_type_push_back
container_type_pop_back   
container_type_push_front 
container_type_pop_front
[download]

…and some more, depending on the container.

If the container is a deq (dequeue) and its type named fubar this would result in deq_fubar_push_back and so on. Instead of a simple push in a well know post-modern language. One may regret this but it is like it is. And I don't know how else to do it. Apart from the fact that I can't write such macros.

Other libraries, like m*lib work similiar - m*lib does this excessively.

«The Crux of the Biscuit is the Apostrophe»

To the other points: I haven't come to any conclusions about how I generally handle this. BTW, the idiom _struct_name type_name uses "C Programming - A Modern Approach" (King 2008) all the time. Like everything else, I didn't come up with it.

«The Crux of the Biscuit is the Apostrophe»