I wanted to try experimenting with fluent interface design in the C programming language. That's why I wanted to ask you, Dear Code Review users, comments on the way I have implement this simple employee record interface.

Please note that for maximum simplicity I am resorting to as simple data structures as possible.

#include <stdio.h>
#include <assert.h>
/* if this weren't just an example I'd make a linked list */

/* global this pointer, there is no way around this */
void* this;

typedef struct Employee {
    struct Employee* (*set_salary)(int);
    struct Employee* (*set_employee_id)(int);
    char* name;
    int salary;
    int employee_id;
} Employee;

Employee* do_set_salary(int s)
    ((Employee*)this)->salary = s;
    return this;

Employee* do_set_employee_id(int id)
    ((Employee*)this)->employee_id = id;
    return this;

typedef struct Record {
    Employee* (*add_employee)(char*);
    Employee employees[MAX_EMPLOYEE_COUNT];
    int cnt;
} Record;

Employee* do_add_employee(char *n)
    Record* this_record = (Record*)this;
    assert(this_record->cnt < MAX_EMPLOYEE_COUNT);
    this_record->employees[this_record->cnt].set_salary = do_set_salary;
    this_record->employees[this_record->cnt].set_employee_id = 
    this_record->employees[this_record->cnt].name = n;
    this = &this_record->employees[this_record->cnt];
    return this;

void init_record(Record* r)
    r->cnt = 0;
    r->add_employee = do_add_employee;

Record* edit(Record* r)
    this = r;
    return r;

void print_record(Record* r)
    int i;
    for (i = 0; i < r->cnt; i++) {
        printf("%s, salary %d, id %d\n",

int main(void)
    Record record;

    /* behold, fluent interface design! */



    return 0;
  • 3
    \$\begingroup\$ The point of fluent is to make the code more readable. This fails on that account. It would be more readable just to use normal methods in this situation (rather than chaining). \$\endgroup\$ – Martin York Nov 24 '11 at 14:46
  • 2
    \$\begingroup\$ I'd also add that fluency often drops the verb (add, set, etc.) , or turns it into something more "human" (with, having, etc.) One of the points is to make it sound "right". \$\endgroup\$ – Dave Newton Nov 24 '11 at 16:26

I would drop the edit function and make add_employee the entry point to the API. I've written a number of fluent APIs in C++ and found that placing the required arguments (e.g., employee name) in the API entry point invaluable. From the usage point of view, something like:

int main(void) {
    Record db;
    add_employee_to(&db, "Bob")
    return 0;

The goal of the API is to create a new employee and append them, so make that the entry point. If you can't have a valid employee record with a name, then this becomes a first-class parameter of the entry point. Not sure about the requirements, so it may make sense for ID to be a required parameter as well. I also changed the names to make them More Fluent™.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.