zklim / 42-philosophers Goto Github PK

this is a good place to use enum.

It may be a good idea to define a fork data structure that contains just that.

Then define functions like fork_take and fork_release that deals with all these mutex. This is an abstraction that allows you to write your code in a much more readable fashion. So your eat function would call those instead.

When I was writing this project, it makes more sense to me to have separate functions to be called when a philosopher take an action, i.e. eat, sleep, think, die. I find this approach to be quite nice, since overally, my code would be quite easily adapted to the bonus part of the project.

I suppose, the way I have written the project is more like an object oriented approach, where a philosopher is an object, and it can take actions.

Forks are also object. Whether they are implemented as mutex or semaphore is an implementation detail. The interface remains the same.

Give it some thought!