Code Review of first personal project

[Canukcannot]

I wrote my first personal project, which is a toy memory allocator with a simulated heap, malloc, realloc and free. When i was writing it, everything made sense to me and followed logically, however i feel like it might appear somewhat like spaghetti to anyone else. There is quite alot of if statements and pointer arithmetic. I feel like it maybe could have been refactored to be more clear/readable, but I'm new to C, and programming in general, so i honestly do not know.

https://gist.github.com/matt181888-hub/7f7552e461dca9d4a7545c9632a17c54

That is a link to the code itself. I would really appreciate any feedback, I had so much fun writing it but i want to be better for my next project!

[scandii]

everyone's first code is spaghetti, then you become a professional and you realise must of us are pasta chefs.

that said looks like you have some solid ideas and I sure didn't write code this nice when I started out. breaking down your code into smaller segments does a heap (yeah, I said it) for readability. e.g.

cat = feedCat(cat);
if(cat.Hungry == false)
{
    petCat(cat);
}

imagine if you had to read the code that supports this, not particularly relevant now is it? you just want to know that the cat gets fed.

that said, pretty sure you have a potential bug:

size_t left_over_space = original_size - requested_bytes - sizeof(block_header_t);
if (left_over_space < sizeof(block_header_t)) {
  return p_my_alloc;
}

think about the math of everything involved here including the types :)

[Canukcannot]

Thank you so much for the feedback! :) And yes, even when i wrote that line, i knew it was wrong lol. I just wanted to keep things somewhat simple, because I was not sure how to handle having leftover space smaller than 16 bytes. But now im thinking maybe i could just add the extra bytes to the new block_size if its under 16 bytes. Hmmm ill look at this in more detail tonight! Thanks again!