Design Patterns for Embedded Systems in C

Within this book there are many 5-star worthy aspects as well as many 1-star aspects. Unfortunately, the 1-star aspects consisted of the majority of this book and took away from the delivery of the material. This major problems with this book can be summed up as follows: The author has an extremely high estimation of his other books and creations throughout his career and wants to reiterate those as often as possible. This created the following problems:1. The first two chapters should be thrown out - a large portion of this section is describing how to make C an Object oriented language and promoting the author's other texts. It would be more helpful to put other texts in a reference section and just use C++, describing the features of C++ to avoid for embedded applications and why. Instead the author reinvents the wheel and wastes the reader's time in the process.2. The extensive use of UML is overkill- the author helped develop UML standards so he uses it in all examples, even if it does not shed any more light on the design pattern in question. I do not like having to learn how to read a diagram in order to read a book. (e.g. I shouldn't have to read online about UML state diagrams when a simple state diagram with a legend will illustrate the point equally well in a fraction of the time) I should be able to just read the book and the diagrams should help facilitate that.3. The book was written in PhD styling - The author will introduce some vocabulary in the middle of a point hes trying to make, which just makes it more difficult to understand.In summary, I would not purchase this book again. If you are considering this book, look at "Real-Time Concepts for Embedded Systems" (ISBN-13: 978-1578201242 ISBN-10: 1578201241) instead. It covers all of the material in this book and then some.

Although I read the reviews about the book before my buying, I still made my purchase, and I was so excited when I received it. I started reading the "theory" about design patterns for few days and I was kind of happy. When it was the time to test the code I got very frustrated because the code doesn't compile (I tried the Observer's Pattern code at page 116). As other reviewers said, the book lacks of structure, no one took the time to compile and test the code, and needless to say that it's very hard to follow the code, even when you download it from the publisher site (it's in Word format, so I needed it to format into raw C text files). The UML diagrams are also hard to understand, and the code is incomplete.There is an errata document, but it's also incomplete.The book's title says "... An embedded software Engineering Toolkit". The book is far for being a toolkit. You will spend hours figuring out how to make the examples to work, and finally you'll release that you can't. Is that a toolkit? I guess it's not. I also think that using the object oriented approach is not really necessary for all the patterns. I found on-line an example of the observer pattern in pure C. Clean and clear, nothing about OOP.No other book talks about design patterns in C for embedded systems, so in that context the book is very valuable. Nonetheless without examples to work with the book is almost useless.My recommendation is that you DON'T BUY THIS BOOK until a new edition is ready, otherwise you'll complain as we've done. By the way, the publisher would give us a free copy of that newer edition for customers that actually bought this first one. (I live outside US, so I needed to pay shipment costs, taxes, currency parity, etc.)

I've been working in Java for the past 12 years and am now returning to C for some project work. C was always my first love and I wish I'd stuck with it.This book struck the right chord for me since it focused on how to do object oriented work using C and not C++ or Objective C. It answered questions that I'd wondered about.I'm used to design patterns books for getting the architectural outlines and best practices for software development so this book works for me in that regard as well. It is going to help me get the structures of my coming projects right.

Good read. The kindle version is not well formatted if reading on android. Reading on the DX was fine. Don't look for a lot of code you can compile and run. The book focuses on architecture and design. Highly recommended.

I am going to have to agree with the points made in Vomkap Biskairo's 1-star review. It's hard to take a book seriously with so many coding typos, since it wastes your time and confuses you(example: pg 116 struct GasNotificationHandle declaration is incomplete). The (in my opinion) overly object oriented handling of every example detracts from key points and makes the code hard to read. Also adding to the difficulty is that there is no syntax highlighting to the code, and the filenames for each snippet appear ambiguously after the snippet equidistant from the next snippet. I also wish he covered singletons--even to a short extent.This book does have some good concepts, but to deal with reading the code with typos and object rich format, I would recommend this book for someone who's very familiar with C and object patterns. If these problems were fixed, I wouldn't hesitate to give it 4 or 5 stars.

if you need a book which tells you about methodology, this book is for you!i am having a lot of answers about all my doubts, with examples given and pretty clear and exaustive discussions