Extreme C: Taking you to the limit in Concurrency, OOP, and the most advanced capabilities of C

4 chapters in and I’m blown away by how much knowledge is in here!!!Edit: As programmers living in 2020, we’re not usually tied to a language. The art and science behind it all is (usually) easily applied to other high level languages, even when we’re not 100% familiar with the syntax. With that said, learning C’s syntax, and even becoming familiar with C’s available functionality in the standard library, is NOT enough to be successful with C. I’ve read “C in a Nutshell” in the past, and while I learned the syntax, I’m now discovering that I knew NOTHING before this book.I also want to say that this book isn’t just a book about a programming language, because it’s also a computer science book. That’s just something that comes with the territory surrounding C. You’re going to learn about memory management, probing the heap and the stack, pulling out hex values from your arrays using gdb, and much more.I love this book, and if you love learning about C, so will you.

I've come to associate Packt as the publisher where anyone with a word processor can get published. This is not one of those books. This is far and away the deepest, most well written text I own on modern C. If there can only be one C book in your collection, this is it (Sorry K&R...). Material is well organized, concepts are clear, and the author's personal philosophies are suggestive rather than authoritarian (although he strikes me as an authority...). I'm 13 years deep in C, and 3 years in on owning this text and I keep re-opening it because the material is that rich. The "OOP in C" chapters are fairly unique for a C book, and probably my favorite sections - they've helped me codify how I think about embedded software stacks and re-usable code. The real "extreme" here, is the simultaneous breadth of topics covered along with their depths. Fantastic resource.

Book has a good and well structured content regarding contemporary C programming (as of 2020)I've completely missed the point of OOP chapters though. I mean - yes you can do OOP in C, pascal or whatever procedural language... even in asm :) suggested approaches do not make object oriented C code look on par with C++. And when someone choses C for particular task he is (in my belief) makes informed decision not to follow OOP style for many good reasons. This is why I give 4 stars rather than 5. In my opinion book would be slimmer and way better w/o those chapters :)

Just get it and read it if your going to do any linux dev work. Covers everything OOP in C, abstraction, polymorphism using function pointers is great. IPC is well presented pipes, sockets and shared memory are covered completely. Making kernel calls is well covered. Using gdb to debug, using strace.The chapters on threads is wonderful and the example code helped alot since I am used to using threads on windows.I am writing CUDA code and this book helped me slog through the NVIDIA C examples.Again this book is indispensable for anyone doing linux development .

This book covers a range of areas that are vital for C programmers to further develop their knowledge and skills. Though they are not covered to great details due to content limit, it is more than enough for readers to have a basic understanding of the topic and use it as a foundation to delve deeper.

the book is introducing concepts and demonstrate them with examples alongwith what could go wrong.laid out very nicely and references for more information is also given in case youfeel the need to go a bit deeper...i recommend reading the first two chapters even if you know some C.[EDIT]i didn't knew C as good as i thoughta must have classic on C.

Thank you for teaching so much in one book and for making it easy to understand 🙏🏽💕

This book is not that extreme and not that well written. I get the feeling that the author was trying to learn the subjects as he was writing about them; not learn more about them but learn them at all. And I also think that he didn’t review/revise earlier chapters after he learned something from his research for later chapters. The whole thing reads like a series of stereotypical tutorials on CodeProject, which is well shy of where a published book should be.A lot of the problems with the writing style should have been caught by the editor. For example, almost every heading is followed with a paragraph whose first sentence is “Now we are going to learn about <heading topic>.” Almost any level of review and feedback from the editor should have fixed that.