Using Two underscrores __ at the beginning is reserved for the Library/Compiler, also _t at the end might be reserved for POSIX headers.

Glad to see the C version of that FSM. Thanks Gary.

Thanks Gary for making this video even though it might not be your most viewed video - really interesting and informative! On the off change this might get pretty redundant now, I would wish for a golang version

Nice, interesting.

THANK YOU

*GARY!!!* Good evening Professor! Good Evening fellow classmates!* Stay safe out there everyone!

Love your videos on programming 😍😍

Thanks - great video on finite state machines! anyone else’s eyes catch the inconsistent formatting around 3:36 with the missing space if found != NULL

There is a really nice programming language called Nim that I'd think you'd like. It has a similar look to Python but with type annotations, but it compiles to C so it is in the ballpark of C performance-wise. The reason I think you'd like it is because it is better fitted for tutorials like this because it is easier to read, especially for people not very experienced in C. It's also safer as it has good abstractions over pointers and such. It does for example pass function arguments by reference if the type is larger than 24 bytes but the compiler won't let you modify it unless you explicitly mark the argument as mutable.

Now you should give an example using the State pattern en.wikipedia.org/wiki/State_pattern

aight

Using a case statement would be easier for beginners to understand and debug.

woo

Bad styled C, please update methods from old old style C to a bit newer C. But honnestly C is a "dead" language. C++ is alive, I would recommand using C++, even for the same code... (C++ is not an object oriented language, so no I don't say : make it in objects...) For good pratice, try to const all vars and create them with the smallest scope possible, and only declare and init them at the same time. These points makes a world of difference for re-reading the code, and in perf.

First

Start-brackets down on their own lines, never spaces after 'if', 'while', etc. But otherwise an excellent video ;-)

Please do Rust, C is extremely dangerous and leads to multibillionaire vulnerabilities every day. No one should code in C nowadays.

Pointers for a state machine? You got to be kidding, man... that's some of the worst advice I have ever seen. The very point of state machines is that they are an ABSOLUTELY SAFE programming paradigm. Inserting a pointer makes this a nightmare to debug.