3 comments about Building Your Own Compiler with C++.

1. 1)This book is a nice one to read for Beginners in this context 2)Ease to understand is extra value to this book. 3)This book edges out many others in this category. 4)I would recomend this book to novice programmers.



2. Though I admittely have the previous print of this book, I am fairly convinced that my judgements of that book hold true for this edition. The C++ code presented here is some of the worst I have ever seen. The earlier chapters actually try to be a crashcourse C++. I got the distinct feeling in later chapters that the author's full knowledge of this wonderful language are unfortunately contained therein.

   The detail level of this book is saddeningly low. Being 112 pages (194 in my edition) this is hardly a surprise anymore.

   Long story short, if you want to see someone write bad but well documented code for a simple compiler, by all means buy this. If you want to know how things actually work, more books will be a necessity. My suggestion for theory: Dragon Book (Aho et al.) and add Holub's "Compiler Design in C" for a practical hands-on, but in-depth approach.




3. Do NOT buy this book... This is really bad.
   
   This was one of my first compiler text I bought around 10 years ago. Don't make the same mistake!
   
   If you're looking for a learning-by-coding compiler text buy 'Programming Languages processors in Java' by Watt and Brown. See my 5 star review there.... Second choice: If you're looking for a C++-book buy 'Compilers and Interpreters' from Ronald Mak.
   
   This are the problems with this book:
   
   * The language of the compiler your build in this book is too simple. There are only 2 statements: assignment statements and writeline statements. So after you study this book you know NOTHING about how to generate code for function calling, passing parameters, records, arrays because all this is not supported! Even things like IF-statement and a WHILE-loop is too difficult for the author. Extending the language with an IF-statement is an exercise, probably because the author couldn't get it working hisself.....
   
   * If the book explains something it's only to clarify the code and not to explain you the algorithms behind it. So it tells you that a Yacc parser is called by the yyparse() function, but this book even don't tell you what parsing is, what methods there are (LL/LR etc), etc. The only you need to know is yyparse(). The author give you a Grammer file, but you may find out yourself how the grammer file is organized (BNF). So after you read this book you will still ask: 'what is parsing? what is scanning? how does Yacc work?' etc. etc.
   
   * It is one big listing and it doesn't explain much.
   
   Conclusion: the compiler is way too simple, the author explain nothing, and after you read this book you will have no more fundamental compiler design knowledge than you had before!
   
   For people which are new to compiler construction will learn nothing, and for people which have advanced knowledge about compiler construction (like me) it's too simple and will discover a lot of mistakes.
   
   Avoid this book!

3 comments about Understanding C++ for MFC (With CD-ROM).

1. I am a CS student looking to do some GUI programing.The first 1/4 of the book is just basic brush up on simple c++ classes,strings, declaring variables, pointers,etc. Nice little refresher. Then it gets into pop up windows which was informative but very limited . Then the remander of the book is focused around one program that he wrote as an example but his descriptions are so vague it is dificult to apply it to your own program. The things done in the book can just as easily be done by following the MFC app wizard in visualc++ and then reading the MSDN library, save your money, or buy my copy used =)



2. The one thing that you're not going to do at the end of this book is actually understanding MFC. It will give you a crash course in how to write an MFC program, and that's where it stops. Deeper understanding of how and why things work the way they work is not explained.
   Most of the book is based on one example, so if you skip a chapter you're doomed because your sample project isn't up to date. I wouldn't recommend buying this book.



3. It does a good job of introducing MFC with good but not many examples. If you know C++ programming and have experience with another GUI framework, this book will serve you very well to understand MFC quickly.

5 comments about The C/Unix Programmer's Guide.

1. well, this book has proven handy for reference and review, but i would certainly NOT recommend it. the author repeatedly used obscure functions(imho) that were prone to bugs, and he introduced totally new concepts in breif 10-word sentences only to use them all-too-frequently in most examples following. yes, im a 16 year-old, shift-key-fearing mexican, but i've seen good code, and mr.bacon's code doesn't fool me. if you want to take full advantage of this book, read the ENTIRE THING in one sitting so every little concept sticks with you throughout, and don't you dare approach a computer without reading a book that emphasizes on structure, organization, and clean, effective code first



2. The C Unix Programmer's Guide was the only book I could find that provided useful background information as well as thoughtful, applicable coding examples. What impressed me most is the fact that all the information found in the man pages on C as well as further insight was combined into an easily readable and searchable format. As a student of computer science, I was familiar with Borland/Microsoft C++, but I had no previous experience with C or Unix. This book helped me get an A (one of three) in Operating Systems! While my classmates struggled on assignments, I was able to find exactly what I needed to complete the assignments on time. I truly believe that without this book I would not have performed nearly as well. Thank you Mr. Bacon for writing such a great book!



3. This book did an amazing job of introducing many important concepts about C, and C in UNIX.
   
   The description of the material is very clear, and the examples are well thought out.
   
   If you're looking for a beginner/intermediate text on C and UNIX, this is THE book to get.



4. I wish this had been my First C programming book. It teaches all the basics required for you to start some worthful programming under *nix. It doesn't go into as many details for e.g., as given in 'C programming: A modern Approach by King but it still gives many details on what things are. It starts with basics of Unix and provides a lot of information on the C development tools in *nix. A very good starting point for learning programming in C under *nix.



5. I have seen good C programming tutorials, and this is not one. It isn't very descriptive. It will introduce you to new library functions and not give a good explanation on it, and then it rarely describes the code snipets. The C Primer Plus by SAMS is far superior to this for learning C. Having said that, this book is decent in its coverage for UNIX system calls with C, in that it is easier for a beginner to understand the code snipets in this book as compared to other books I have seen. Other books I have seen require you to at least already be an intermediate C programmer, and use examples that require you to study the complex code snipets before you can begin to understand what is being accomplished with the system calls.
   
   The author/publisher hasn't updated this book with regard to hardware, and it talks about 286's, 386's, 486's and Pentium processors. It considers 16 bit and 32 bit processing, and it puts too much emphasis on 16 bit, when every compiler I have seen for C is 32 bit. It even gives suggestions based on 16 bit technology. It references DOS, and if anyone is still running DOS, they shouldn't be reading a book about programming. They should be reading about survival skills and moving to Montana and building a bomb shelter.
   
   So, to learn C, this isn't a good book. If you are dealing with the C/UNIX environment and are a beginner, the end of this book is decent for understanding system calls, as long as you already understand C from some better, more up to date source.

5 comments about Standard C++ IOStreams and Locales: Advanced Programmer's Guide and Reference.

1. I've never seen a more thorough book. It's amazing just how much information there is on one topic. If you really want to use the iostream library, you have to have this book.



2. The reason why I bought this book was the wish to learn more about the C++ Standard. When I held the book in my hand the first time I was not shure if it would be worth the time reading it. It seemed only be useful for a DOS - like software, not for my GUI problems.

   So I was very surprised in a good sense to read about ideas how to use IOStreams for GUI - internationalization (I18N), described on pages 175 and 225. The IOStreams library, as it is described by the authors, is a better answer to my I18N - problems than all other three GUI - libraries I know. It offers more flexibility.

   An other treasure was the techniqe of two-phase polymorphic dispatch described in this excellent book. This technique allows me a much more flexible design than in the past. If the customer asked for new features I often had to change my class hierarchy (and all classes in it) by adding new virtual functions. It is cumbersome if it is code of a library. The two-phase polymorphic dispatch shows an alternative.

   The third (but not the last) treasure are the appendices. They are a good reference for C++ refinements.

   The thought I perhaps would not have read this book worries me, I had missed a chance.

   Many thanks to the authors writing such an excellent book.




3. When people think of C++ standard libraries, they think of the STL. There are dozens of books on the STL, and everyone is taking advantages of its features to get good algorithms that don't reinvent the wheel.

   As this book points out, IOStreams is perhaps the most-overlooked part of standard C++. It has just as many features as the STL, and can help you write less, better code if you take advantage of it. If you have ever spent a few days writing a buffer class, you didn't have to; The IOStreams streambuf is comletely extensible and customizable.

   Even better, IOStreams is a complex, high-performance library written by a C++ expert from Bell Labs. Most of us C++ programmers don't think about how IOStreams works, other than to write '<<' a few times. OO design doesn't get any better than that. This book is also an excellent case study on the IOStreams library, touching on the proper use of multiple inheritence, and the benefits of static type checking. If a library can be this efficient and extensible, while being as easy to use as typing '<<', there is something every C++ programmer can learn from its design.

   The book is even endorsed by Jerry Schwarz, the man who invented IOStreams, and has a forward written by him. If you own two STL books, but not this book, I think you've made a mistake. This should be the third C++ book you buy, after a language reference and STL reference. It is that useful and interesting.




4. The title of the book says it all. This book delivers anything you could possibly want to know about streams and locales. The book might seem dry at times but im so glad I muddled through this book the first time; i cant imagine programming with out it!

   You will be able to write flawless file I/O thats easily extensible and maintainable. All with less code than the C-style I/O. Almost all C++ books teach C style I/O for some reason, and you will cringe at that after you absorb this book.

   You will be able use your new code with the STL seamlessly giving you even more robust and easy to maintain code. I still get giddy when i see how elegant and flawless your code can be when you use the standard library (the non-depracted part) to the fullest.

   The auther points out that some example code may not work on MSVC++ 6.0. Well, thats what i use and found little code i cant compile without modifications; and the code you cant compile you will be able to figure out good workaround right away if you know what VC 6.0 cant do; even I found good workarounds.

   You may think Iostreams and locales arent worth knowing about if you program windows apps. This is wrong.

   This book is good in so many ways, even the appendiecs were great source of new info. I still reach for this book at least once a week. This is my best buy period.




5. The authors has excellent knowledge of the subject, but that is sadly not of benefit for this book, on the contrary it is its problem. The book seams to be written in the following way:
   1. Rewrite iostreams header files as english text instead of c++.
   2. If at any point, you can make a long remark about some detail, do so. The longer the better.

   Usually when an author it trying to make a book as thick as possible, it is done by adding redundant words to make it easier to read, not in this case, the sentenses have no flow, its just a large collection of words.

   I would recommend reading this book to anyone implementing the subject from scratch (for his own compiler) and to people stranded on desert islands. The rest of us can read existing header files, contemplate them and still have time to spare.

   Life is too short for spending time reading the same thing i just read, over and over again.

5 comments about Visual C++6 for Dummies.

1. If you already know C++ and want to learn to make programs that run in the Windows GUI instead of a command line, this book DOES NOT cover that. The most advanced example program provided runs at a command line ! If I had known that, I would not have purchased this book. The book barely touches on menus, buttons, etc, and does not cover how to write a complete Windows program that uses the GUI.

   If you don't know C++ at all and want to learn it, this book has lots on C++, but there are much better books out there for learning C++. The coverage of C++ in this book is not sufficient to teach it to someone who is learning it for the first time.




2. This book is pretty good on C++ syntax, but doesn't do much on actually getting into the MFC and Windows programming side of things. I would highly recommend Sam's Teach Yourself Visual C++ 6.0 for learning the basics of MFC programming.



3. I bought this book with the notion of learning Visual C++ 6.0 in my spare time. I was very disappointed. There are a lot of examples but some did not compile. I worked every example in the book but I do not see how some of these examples fit into the big picture. The book may have been better if the author had chosen 1 specific example and then built upon that example to give you a real-world application. The examples in each chapter had nothing to do with the examples in the chapters before it. The author just shows you several different ways to accomplice the same thing.



4. This is undoubtedly the worst C++ book I have seen. It spends so much time being cute and funny (well TRYING to be funny) that it fails to teach the material. It is broken up into many little incomprehensible parts. Each part has a name that does not tell what it is about because the authors are trying to use silly little puns for titles. Nor does the order of the parts contribute to learning anything.
   After reading this (well trying to read it) I was more confused than when I started. Stay away from this one at all costs. A better choice is Beginning Visual C++ 6 by Ivor Horton.



5. Ok. i know its called "for dummies".... and i dint really consider myself one, until i dropped $29.99, but, i looked at the first few chapters, and it look OK.... I thought id get much more "Windows programming" out of it

   i got a bit tired of :
   "see me feel me touch me print me..."
   "smooth operator"
   "holy debugger batman, it works... etc...

   A bit to bubble-gummy for me AND, as was mentioned before:
   What About Windows ???? ... id didn't buy it Strickly for c++, it said "VISUAL c++"... maybe if it had been called "Visual c++ console apps", (which is what it is) i would have (should have), left it on the shelf.. maybe its my fault... i guess when i think visual c++, i think sdi, and mdi classes...OH... maybe i am a dummy, after all

   I was NOT amused, nor very happy...

5 comments about Starting Out with C++ (3rd Edition).

1. This book is very, very exhaustive in its coverage. I didn't even go through a part of it. But aside from its bulk, it was a very good introduction to programming. Gaddis does an excellent job of showing how to program step-by-step, and makes it easy to teach yourself.

   The book also contains a quick reference section where you can look up frequently used commands without having to find them in the text. This book is highly recommended for beginning (and even continuing) programmers.




2. Since class has started I have only been able to attend half of my classes. While I love to program I was worried about missing the lectures. This book is very well documented in a step by step fashion that I have been able to stay at home and study, do my homework and maintain an excellent standing in the class. Compared to introductory books I have read in the past "Starting Out with C++ (3rd edition)" this actually allowed for me to grasp the basic concepts of the language. It will always have a place in my library.

   Aaron




3. I found this textbook to be very poor, especially for a beginning programming course. It presents concepts in a confusing fashion and presents simple TOO MUCH information sometimes for students to digest. It isn't an accessible text for students starting to learn C++ -- it blurs concepts which are useful and essential with concepts which really aren't necessary. Many of the examples are poor, and the presentations of functions and classes are particularly poor. If you are looking for an accessible and clearly-written Computer Science I textbook, try Rick Mercer's Computing Fundamentals with C++. I highly recommend that book; I do not recommend this one.



4. This book discusses wide range of topics, covering most aspects of C++ programming. At the same time the auther is meticulus and has dealt with the topics in depth covering finer points.

   Many solved examples and additional excercises are given. The whole book is linked with a project, so the students will get to know how and where to apply (in real world situation) the topic which they have studied.

   Excellent for both teachers and students.

   Highly recommended.

   -Prof. M.G.BHATIA




5. I've been developing software for about 15 years now and I needed a refresher in C++. The bad is that this book didn't help me until about Chapter 11 (remember that all you C jockies out there). The good is that I would definitely recommend this book to anyone starting out programming at any level (including a novice). Excellent book.

2 comments about Beginners Guide to C.

1. Out of every book on programing I've ever tried including .Asm & .c this is the best. It will teach you well and help you build great habits as well. It also gave me a generally much greater love of programing. How many books do that?



2. The only thing that kept this book from rating five stars was it's lack of a function list\description section. An appendix to this end would've been nice. This book made learning 'C' quite easy.

4 comments about Beginning C, Third Edition (Expert's Voice).

1. Notice something strange in the computer section of bookstores? Plenty of books on such languages as Java, C++, C# and Visual Basic. But try finding a book on plain old C. Perhaps there is an issue of Kernighan and Ritchie. But, quite possibly, there is no C book at all.

   But a need for C still exists. Most of the unix variants, and linux, are coded in C, with perhaps a C++ overlayer. And on Microsoft machines, a vast body of C code also exists, for such things as device drivers, for example. K&R is the definitive text for C, but awkward for users new to any programming. Its terseness and lack of many examples make it so.

   Which is why it is nice to see a new edition of Horton's book. It deliberately eschews the conciseness of K&R. Instead, it has extensive discussions of every feature of C. Aimed squarely at a newbie. Horton is generous with code examples, many of which are entire (small) programs. Naturally these days, the code can be downloaded from the publisher.

   Horton even discusses what may be fairly advanced stuff for a beginner. Like structuring data via the struct command. What this means, though, is that the book can be used as a complete text for the language.

   As an important practical matter, you do not need to understand all, or even most, of the book, to start coding. The emphasis from the first chapter is on writing code, even with only partial knowledge of C.

   Purely as a conjecture, it may be astute planning on the part of Hortan and his publisher to come out with this edition. A real gap seems to have opened up in the market over C books. This might fill it.




2. This seems to be a rewrite of his earlier edtion, Beginning C. There is no mention whatsoever of the new C99 standard, etc. It looks as though they put a new cover on the book and raised the price. BAD, BAD, BAD!!!!



3. I'm currently reviewing my C for a new position, and am appreciating this book very much. When I learned C in community college, we used poorly written unfriendly textbooks. While Beginning C may not be a "must have" book, it's part of the generation of approachable books beginners can use, with substantial examples usable by intermediates.
   
   I'm primarily retyping in the code (although I could download the electronic form) to introduce bugs and practice my debugging skills. I **have** noticed that some programs have bugs or needed minor changes to run on my CodeWarrior C platform, but I see this as a feature, not a bug. :D



4. I recomnd this book, it was easily twice as good as any online tutorial you could have taken.

5 comments about GDI+ Programming: Creating Custom Controls Using C#.

1. This is the kind of book you want to read when you want to get started with GDI+ development, and custom controls in particular. Yes, there are a lot of things that are not explained, but they, GDI+ and custom control development is a huge topic and couldn't possibly be covered in one book! The information provided in this book is excellent. It covers the basics of GDI+, custom control development, printing, and even web related stuff you may not think of at first. What's missing is how to build input-oriented controls, such as as fancy grids or spreadsheets and other advanced topics. But then again, I wouldn't expect a book like this to cover these topics.



2. One of my first .NET ah-hah experiences back in 2001 was creating an .aspx file that I could reference as a graphic (!). The .aspx file received two query parameters which informed it of the file name of the jpg and the width that the returned image was supposed to be. So then in an IMG tag, I would simply put src="ShowPicture.aspx?file=product1343.jpg&width=100" and it would display a thumbnail of that picture 100 pixels wide and proportionally high. This is an excellent way to produce dynamic pictures as well as protect your online photographs (show thumbnails to visitors, full sized pictures to members), and the .NET GDI+ classes are straight-forward and easy to use. Ever since then I have been looking for a book which goes into deeper detail of creating graphics in .NET with the GDI+ classes. Wrox has finally produced this book! In chapters 1 through 10 you get the basics: pens, brushes, texts, fonts, image manipulation, paths, regions and printing. Then in the rest of the book you learn how to make custom controls which create custom graphics (I love books that teach two things at a time -- great for developers who do four things at a time). If you read this book, you will think about graphics differently, namely, as dynamic objects which your application, the user and the environment can manipulate at run time. Very exciting.



3. It delivers what it promises. You will be able to write printing code, make your own controls, etc., after reading this book.



4. GREAT BOOK! The book was by far the easiest to follow book for GDI+ and Custom Controls using C#. I am very pleased and highly recommend this to all who wish to learn GDI+.

   If you are moving up from GDI, you will find that GDI+ is about 50 times slower, but 50 times easier to program.




5. This book is easy to read and very practical. It helped me a lot with one of my data charting projects. Highly recommended.

1 comments about Modern Compiler Implementation in C: Basic Techniques.

1. This book provides a great overview of compiler-writing in general, with excellent discussions of issues like parsing, code generation, register allocation, and optimizations. This particular version (the C version) of the book, however, seems to contain a lot of typos in the code samples -- even without a compiler, I could see that most of them will not compile. If you can figure out what he meant, however, the algorithms are very sound.