|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
Design Patterns for Embedded Systems in C
und über 1 Million weitere Bücher verfügbar für Amazon Kindle .
Erfahren Sie mehr
| |||||||||||||||
Ingenieurwissenschaften von Elsevier |
Wird oft zusammen gekauft
Produktinformation
|
Mehr über den Autor
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
› Besuchen Sie die Seite von Bruce Powel Douglass auf Amazon
› Besuchen Sie die Seite von Bruce Powel Douglass auf Amazon
Produktbeschreibungen
Kurzbeschreibung
A recent survey stated that 52 per cent of embedded projects are late by 4-5 months. This book can help get those projects in on-time with design patterns. The author carefully takes into account the special concerns found in designing and developing embedded applications specifically concurrency, communication, speed, and memory usage. Patterns are given in UML (Unified Modeling Language) with examples including ANSI C for direct and practical application to C code. A basic C knowledge is a prerequisite for the book while UML notation and terminology is included. General C programming books do not include discussion of the constraints found within embedded system design. The practical examples give the reader an understanding of the use of UML and OO (Object Oriented) designs in a resource-limited environment. Also included are two chapters on state machines. The beauty of this book is that it can help you today. Design Patterns within these pages are immediately applicable to your project. It addresses embedded system design concerns such as concurrency, communication, and memory usage. Examples contain ANSI C for ease of use with C programming code.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
In diesem Buch
(Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Vorgeschlagene Tags zu ähnlichen Produkten(Was ist das?)Setzen Sie den ersten relevanten Tag hinzu (ein Schlüsselwort, das mit diesem Produkt in engem Zusammenhang steht).
|
Kundenrezensionen
Die hilfreichsten Kundenrezensionen
3 von 3 Kunden fanden die folgende Rezension hilfreich
Format:Taschenbuch
Bruce Powell Douglass, eine Ikone der Softwareentwicklung bei IBM, hat mit diesem Buch versucht, bekannte Entwicklungsmuster (Patterns) die ursprünglich für objektorientierte Sprachen entwickelt wurden, auf C zu portieren. Hierzu wird noch im einführenden Kapitel beschrieben, wie man C Objektorientierung, Vererbung, Polymorphismus und weitere Errungenschaften der objektorientierten Programmierweise "unterjubeln" kann, was zeitweise bizarre Züge annimmt.
In folgenden Kapiteln werden verschiedene Patterns sehr anschaulich und mit (sehr viel Zeilen abgedrucktem) Quellcode erläutert. Von jedem Pattern werden Vor- und Nachteile ausführlich diskutiert,
Dieses Buch ist **zu empfehlen** für Leute,
- die lernen wollen, wie Patterns funktionierten
- die verschiedene Patterns kennen lernen wollen
- die wissen wollen, wie man aus C eine Objektorientierte Programmiersprache macht
Dieses Buch ist **nicht zu empfehlen** für Leute,
- die strukturierte C-Programmierung mit vertretbarem Aufwand durchführen wollen
- die bisher noch keinen Kontakt mit C++ oder Java hatten
In folgenden Kapiteln werden verschiedene Patterns sehr anschaulich und mit (sehr viel Zeilen abgedrucktem) Quellcode erläutert. Von jedem Pattern werden Vor- und Nachteile ausführlich diskutiert,
Dieses Buch ist **zu empfehlen** für Leute,
- die lernen wollen, wie Patterns funktionierten
- die verschiedene Patterns kennen lernen wollen
- die wissen wollen, wie man aus C eine Objektorientierte Programmiersprache macht
Dieses Buch ist **nicht zu empfehlen** für Leute,
- die strukturierte C-Programmierung mit vertretbarem Aufwand durchführen wollen
- die bisher noch keinen Kontakt mit C++ oder Java hatten
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
5 Rezensionen
18 von 18 Kunden fanden die folgende Rezension hilfreich
Wait for a 2nd edition...
19. März 2011
Format:Taschenbuch
I've read only 120 pages so far and decided to already post my review anyway.
The book performs a rather good job in presenting a catalogue of design patterns for embedded systems: each pattern is provided with C code examples, an UML diagram, some clever explanations about its benefits, hints for its implementation, related patterns with which it can be combined, and other useful information.
The author chose to structure his code as object-oriented whenever possible, even for the classes that will clearly never be instantiated more than once. This results in having in every function a parameter for the object on which it must be applied and a lot of pointer dereferencing that makes at my sense the code heavier to read.
In addition, for a book about embedded systems, I would expect variables qualified as volatile when it is required, when accessing memory-mapped I/O for example (p. 83). The text has some typos (p. 81, "high-ugency" or "distribition") and some errors (p. 111, observer pattern: "the clients simply offer a subscription function that allows clients (...)".
If I had to stop my review of the book at this point, I would probably give it 4 stars.
Unfortunately I am not. I got rapidly annoyed of continuously reading so badly formatted code. The indentation and braces are set completely at random throughout the whole book. On page 29, the author shows the overall structure with some completely wrong pseudo code: "Switch", missing case statements, a strange "If { ]" block... Moreover there are a lot of strange constructs and approximations in the code snippets: useless nested blocks {{ }} (p 56); for (p. 20), if (p.72) and while (p. 71) statements finished with a semi-colon; '/n' instead of '\n' (p. 117); #endif without corresponding #ifdef (p. 105); side-effects in printf (p. 20); on some pages the keywords and function names are highlighted, on some other not, etc, etc, etc.
The book has been printed although it was clearly not ready for that. Come on, even the link to the editor webpage on the back cover is wrong (have you ever heard of the htpp protocol: "htpp:/ www.newsespress.com")! I'm not willing to read a book that has not been reviewed well enough; therefore I give it the minimal rating.
Bruce, fix the typos, clean your code, release a second edition, and you will get your 4 stars...
The book performs a rather good job in presenting a catalogue of design patterns for embedded systems: each pattern is provided with C code examples, an UML diagram, some clever explanations about its benefits, hints for its implementation, related patterns with which it can be combined, and other useful information.
The author chose to structure his code as object-oriented whenever possible, even for the classes that will clearly never be instantiated more than once. This results in having in every function a parameter for the object on which it must be applied and a lot of pointer dereferencing that makes at my sense the code heavier to read.
In addition, for a book about embedded systems, I would expect variables qualified as volatile when it is required, when accessing memory-mapped I/O for example (p. 83). The text has some typos (p. 81, "high-ugency" or "distribition") and some errors (p. 111, observer pattern: "the clients simply offer a subscription function that allows clients (...)".
If I had to stop my review of the book at this point, I would probably give it 4 stars.
Unfortunately I am not. I got rapidly annoyed of continuously reading so badly formatted code. The indentation and braces are set completely at random throughout the whole book. On page 29, the author shows the overall structure with some completely wrong pseudo code: "Switch", missing case statements, a strange "If { ]" block... Moreover there are a lot of strange constructs and approximations in the code snippets: useless nested blocks {{ }} (p 56); for (p. 20), if (p.72) and while (p. 71) statements finished with a semi-colon; '/n' instead of '\n' (p. 117); #endif without corresponding #ifdef (p. 105); side-effects in printf (p. 20); on some pages the keywords and function names are highlighted, on some other not, etc, etc, etc.
The book has been printed although it was clearly not ready for that. Come on, even the link to the editor webpage on the back cover is wrong (have you ever heard of the htpp protocol: "htpp:/ www.newsespress.com")! I'm not willing to read a book that has not been reviewed well enough; therefore I give it the minimal rating.
Bruce, fix the typos, clean your code, release a second edition, and you will get your 4 stars...
3 von 3 Kunden fanden die folgende Rezension hilfreich
Poor code download - and what about #include "mutex.h"
24. Dezember 2011
Format:Taschenbuch
The short: By all means, buy and work through Test Driven Development for Embedded C (Pragmatic Programmers) by James Grenning before you buy this book. You will not regret it.
The long: Powell's book is full of extensive code examples, which is a good thing. But, to my surprise, the code downloads are in MS Word format. About the only advantage of this is, that you can relatively easily correlate the sample code to the book.
The main drawback, however, is that this code in the you get it, has never been compiled, linked, or tested in any shape or form. Definitely, NEVER.
The include file "mutex.h", in particular, is referenced dozens of times in example code. From what I can tell, it is Powell's own version of a mutex implementation, but there is NOTHING in the book or in the code, not even pseudocode or anything. Basically, this means that dozens of examples are impossible to compile unless you improvise your own mutex.h (easy), and they are impossible to link or test, unless you also design your own implementation of Powell's mutex.
Up to this point, I would still have given the book 3 points, because it still contains a lot of useful stuff.
Enter the publishers: Elsevier, "Addison-Wesley" and their likes. I would give them a minus-two rating, if it were possible. They are no longer reader-oriented, and delegate the real reader support to third-party sites, which leave to be desired as well. As for Elsevier, they seem to specialize in medical books, and little else. Why would they even want to publish this book? As for "Addison-Wesley", just enter enter their web address into your browser, and you will be delighted to find yourself at Pearson, merrily offering you "Solutions for higher education" instead of what you used to be able to find at a publisher's web site. No browsing their books, no decent support, no contacting the author, no discussion group, no discounted eBook upgrade for owners of a hard copy, no nothing, no thank you (funnily, their German site at least allows you to browse and order books, at least).
Finally, there is no reference to the editor webpage or the code download in the eBook, so if you don't own the printed copy, or you don't happen to have it with you, unfortunately you are out of luck...
Having subtracted the publisher's score from the book' score, unfortunately that leaves only one star.
The only reason I bought this book is that currently there are no alternatives, and I already own "Test Driven Development for Embedded C" by James Grenning, which I definitely recommend you buy and study first, before tackling Powell's book. It also gives a better introduction to using object orientation in C than does Powell's book and, in my opinion, a few much more elegant examples. Pragmatic Programming are excellent publishers and you will enjoy everything that the publishers of this book chose to neglect.
The long: Powell's book is full of extensive code examples, which is a good thing. But, to my surprise, the code downloads are in MS Word format. About the only advantage of this is, that you can relatively easily correlate the sample code to the book.
The main drawback, however, is that this code in the you get it, has never been compiled, linked, or tested in any shape or form. Definitely, NEVER.
The include file "mutex.h", in particular, is referenced dozens of times in example code. From what I can tell, it is Powell's own version of a mutex implementation, but there is NOTHING in the book or in the code, not even pseudocode or anything. Basically, this means that dozens of examples are impossible to compile unless you improvise your own mutex.h (easy), and they are impossible to link or test, unless you also design your own implementation of Powell's mutex.
Up to this point, I would still have given the book 3 points, because it still contains a lot of useful stuff.
Enter the publishers: Elsevier, "Addison-Wesley" and their likes. I would give them a minus-two rating, if it were possible. They are no longer reader-oriented, and delegate the real reader support to third-party sites, which leave to be desired as well. As for Elsevier, they seem to specialize in medical books, and little else. Why would they even want to publish this book? As for "Addison-Wesley", just enter enter their web address into your browser, and you will be delighted to find yourself at Pearson, merrily offering you "Solutions for higher education" instead of what you used to be able to find at a publisher's web site. No browsing their books, no decent support, no contacting the author, no discussion group, no discounted eBook upgrade for owners of a hard copy, no nothing, no thank you (funnily, their German site at least allows you to browse and order books, at least).
Finally, there is no reference to the editor webpage or the code download in the eBook, so if you don't own the printed copy, or you don't happen to have it with you, unfortunately you are out of luck...
Having subtracted the publisher's score from the book' score, unfortunately that leaves only one star.
The only reason I bought this book is that currently there are no alternatives, and I already own "Test Driven Development for Embedded C" by James Grenning, which I definitely recommend you buy and study first, before tackling Powell's book. It also gives a better introduction to using object orientation in C than does Powell's book and, in my opinion, a few much more elegant examples. Pragmatic Programming are excellent publishers and you will enjoy everything that the publishers of this book chose to neglect.
2 von 2 Kunden fanden die folgende Rezension hilfreich
definitely not polished at all
29. August 2011
Format:Taschenbuch|Von Amazon bestätigter Kauf
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.
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.
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
|
|
Ähnliche Artikel finden
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
