1 comments about Just Enough C/C++ Programming.

1. Are you a beginner or intermediate C and C++ programmer? If you are, this book is for you! Author Guy W. Lecky-Thompson, has done an outstanding job of writing a great book that provides you with just enough information on the subject of C/C++ in hand to be useful in the real world.
   
   Lecky-Thompson, begins by showing you what the tools of the trade really are, some of the basic concepts related to the programming process. Next, the author focuses on the programming primer. Then, he covers some of the various concepts that make up the typical C program. The author continues by showing you how information is stored in a program. In addition, the author introduces you to Console I/O--showing you ways to get information from the user and display it on the screen. He also shows you how to selectively perform tasks based on the outcome of preceding tasks, which is vital in programming. Next, the author covers mechanisms that are available for task repetition. Then, he covers standard libraries. The author continues by providing you with a detailed explanation of how programs process incoming arguments; and, how you can create functions within your programs. In addition, he deals with file I/O--which deals with ways to process files and perform external data storage. The author also shows you how you can create your own templates for storing information. Next, he looks at pointers--which is an advanced programming topic, but necessary for understanding the bridge into C++. Then, the author looks at pre-processor directives--which detail how you communicate with the program charged with taking your code and turning it into an application. He continues by discussing the extensions to C that make C++ a useful language. In addition, the author gives you some direction as to how you can go about using all of this information. Finally, he provides a list of all the various useful Web references.
   
   This most excellent book provides vast amounts of reference material. What's most important though, is to use the source code from the companion Web site, and click on the Downsload button.

5 comments about Serial Communications Developer's Guide.

1. This book has lots and lots and lots of good information.

   I read a few of the beginning chapters on serial port communications, and then skimmed stuff about the history of RS232, including BIOS interfaces, etc...

   The thing that i found amazing was the variety of information. The author, for example, actually includes a home-brew windowing system. you can tell that this guy loves to do what he does, and he likes to think about *every* part of the system, from the O/S, to the user interface, to the software design.

   I went to the Win32 section, since I wanted to use the windows communications API. I was able to write my application in less than 7 days!, so its better than a "in 21 days book!" however, i have been using Win32 for quite some time.

   i also got, and will probably return, Serial Port Complete because I have Parallel Port Complete (a gem) and the content seems to overlap.

   the Serial Communications Developer's Guide, IMO, will awe you with both minute technical detail as well as a good dose of pratical system level insights!




2. First of all, I have to say that this book provides you with a lot of details about serial communications. It even provides you with a complete library so that you can write the serial communication programming in half an hour.

   The bad part is that I found later that Microsoft had included a MSComm control with VB and VC and it makes the library provided by this book useless. I used the library to write my project and it worked. Then I tried MSComm control and found that MSComm control was better than the library provided by this book. MSComm class gives you more control and it's much easier to use. eg: you don't have to worry about the multithreading because MSComm control has done that for you.

   So, IMHO, if you are a VC or VB programer and you only want to write some simple Win32 serial port program, you'd better use MSComm control instead of turning to this book.




3. Although the book requires a lot of reading, it describes the use of the CD's source code in great detail. Included source code is for both DOS applications, DOS programs running as "Terminal" applications under Windows as well as for Windows applications.

   Microsoft's MSComm Active X is ok where dialog based Windows applications are desired. But in a Windows 98 application that rapidly sends, receives and checks incoming data without user input, this software is an absolute MUST to have.




4. I bought this book to learn how to program Win32 serial communications. It's obvious that the author knows his stuff. Chapters 3 thru 9 apply to MS-DOS and are not really relevant anymore. Otherwsie the source code is a excellent study in how to write a class library in C++ in addition to multithreading which, by themselves, make the book worth the price.

   I used the libraries to write an ActiveX control that has an interface that only a FoxPro programmer would love. My money was well spent.




5. I recently purchased this book for my Meng Project, involving
   controlling a vision head focus,zoom through a pic serial port connected to a pc with vision modelling.
   I am surprised, that the code is written in a fashion which is
   totally unbearable, hard to understand and just reflects the authors perception and imagination rather than discussing the
   important communication building blocks and instructions.
   Its totally ambigious to distinguish the original c++ routines and the invented commands written in form of classes.
   I think if i read through all that material in header files i will lag so behind completing my original project.....
   The paper quality is poor and not very pleasant to read.

5 comments about Maximum MIDI : Music Applications in C++.

1. It is too bad that a book so carefully written and well explained as this one is plagued by two major flaws:

   1) the reader/user is forced to use Messick's toolkit. It has to be said that it works: everything in the companion CD runs and compiles, including the example sequencer. But that's not what I, among others, expected: I expected an in-depth treatment of the standard VC/C++ MIDI primitives and functions, out of which to build my own applications. I could show that it's possible to do so, I have started with a few examples. Hence the book is not useful for someone who wants to start from scratch.

   2) The method for the timing is a kludge. I follow Messick's reasoning that multitasking systems like Windows do not garantee precise timing, but not his solution to use 16-bit, Win3.x thunks. That is a non-universal trick - which e.g. won't work for NT. Now I am not familiar enough with the innards of Microsoft systems to suggest an alternative solution, but I am sure there is a better one. After all, there are plenty of other sequencers (Cakewalk?) that work under all of them. In UNIX, you'd write a driver with sections of code that are shielded from any interrupt and run in real time - in addition, 2.9 BSD has the ``rtp'' (real time process) system call that locks a process, and earlier machines allowed direct access to the clock from a C program.

   To conclude, the book is great if one wants to follow what Messick has done - one may suspect he developed that toolkit for some other reason and then decided to make an extra buck by plublishing it - but it's not " the programmer's definitive source of information for developing MIDI-based Windows 95 applications." And that's too bad because, given the scant documentation by Microsoft, there is ample need for such a book.




2. I've been reading through the MSDN Library documentation (available online if you want to look it up), and there's an article about MIDI timing (under Technical Articles/Multimedia) that specifically advocates using thunking on 95/98 platforms. NT doesn't have the same 32-bit latency issues, and their suggested solution to NT interoperability is to have both 16 and 32 bit DLLs, and switch between them based on OS.



3. First a note. The main purpose of this book is twofold. It's a good introduction to MIDI and using it in windows 95/98, but it doesn't go into detail of how windows does everything. Rather its a documentation for a library of functions that do all the hard work for you and let you get on with writing good MIDI applications. The source code is provided and the author leaves a VERY generous lisence on the software, allowing you to do nearly anything with it!

   Now a word on the writing. This book is perfect, the author uses subtle humor to keep the reading light, but not so much as to make it pathetic. He keeps the tone of the book informal, more as a friend explaining something than a professor lecturing. Despite being filled with facts and details and source code, the book reads like a novel.

   The chapter that simply describes an overview of the MIDI spec. makes for a great intro to MIDI, even for people who have been using it for years. If you ever plan on learning anything about MIDI and how to write computer programs that use it, buy this book.




4. This book hovers between three and four stars in usefulness, but ultimately I decided to give it four stars because it is the only one of its kind. As you probably already know, MIDI is an industry-standard electronic communications protocol that defines each musical note in an electronic musical instrument such as a synthesizer, precisely and concisely, allowing electronic musical instruments and computers to exchange data, or "talk", with each other. MIDI does not transmit audio - it simply transmits digital information about a music performance.
   This book is not a MIDI primer, nor is it about how to use existing MIDI applications. It is about how to program applications in C++ that use MIDI. It does begin with an in-depth explanation of how MIDI works in chapters one and two, but then proceeds into the nuts and bolts of programming.
   Both the book and the toolkit are in desperate need of another edition, since both concentrate on Windows 95 pre-DirectX style-programming. In fact, the author's toolkit is very entrenched in Windows 95. This to me is the book's largest shortcoming. The author does go into great detail to show you how to do common MIDI tasks using his toolkit, including fundamental algorithms for musical timing, toolkit-based synchronization, recording and playing MIDI events, and finally writing sequencers. Complete sourcecode for the toolkit is included on the accompanying CDROM. The author does a very good job of documenting his code and his method, which makes it ideal for what I am trying to do with it, which is adding some additional MIDI functionality to a Java program I am writing above and beyond what Java Sound does. Most of the work involves crow-barring the code's algorithms loose from all of the Windows-centric stuff. If you have similar needs, there just isn't a better or more detailed source in print, and with the advent of full-fledged music applications like Mac's GarageBand, there is not likely to be.



5. I don't recommend this book for the novice. Like others who have reviewed this book, it seems more of an explanation of how to use Paul's higher level routines than a down to earth book on how to understand or write your own MIDI program.
   But it's still probably the best book of it's kind out there, if you can even find another one. Getting any information out of those who know how to write a MIDI program is like pulling teeth. They either don't have the ability to explain it to anyone else, or they're hording the knowledge to keep down any competition. (kind of like an economist, no one can understand them...remember Economics class?)

5 comments about Sams Teach Yourself Database Programming with Visual C++ 6 in 21 Days.

1. This is a great book if you have MFC programming experience but very little database knowledge. It's as if the book was written for me. It's easy to read and it's a great introduction to database programming. You'll learn about SQL, ODBC, OLE DB, ADO, etc. I'll admit that I used to get mind-boggled by this "acronymic hell", but this book gives a great overview and everything finally makes sense. It helps if you have some understanding of COM (ie: what it is and what it's for), but it's not required as it's covered in later chapters. The author presents pros and cons of many different database technologies and provides clear programming examples. Obviously the other reviewers that complained about the examples didn't bother *reading* the book. Some of the examples require that you modify the code depending on where you've installed the sample files. However, these guys probably thought they could learn everything about database programming by cutting and pasting the example code into their programs. I would think that if you're going to buy a book, you should seriously consider reading what's inside...especially if you intend to add "database programmer" to your resume. Duh!



2. This book is a total waste of time and money. The examples in the book are so high level that they don't get down to the details needed in writing a good database application. The book fails to explain any of the object functions or their arguments so you must research the information yourself in A DIFFERENT BOOK. The examples compile but don't necessary work. Don't WASTE YOUR TIME LIKE I DID.



3. If you're reasonably experienced with C++ (in the Windows realm) but lacking in knowledge of the latest Microsoft database technologies, this is a terrific book to buy. I found the examples to be helpful, and the way the book is written makes it seem like you have a Guru right over your shoulder helping you along.

   I strongly disagree with the negative reviews presented on this book; I found the text to be accurate and informative and the text covered a variety of useful topics. Those who had trouble getting the demonstrations to work properly may want to brush up on their basics* a bit, although this book doesn't require overly extensive knowledge of MFC.

   * (Such as actually stepping through the code to see that the problem was your fault.)




4. This book is one of the few that gives you a C++ approach to ADO for accessing databases.

   While I'm semi-comfortable with the Windows internals (thanks to Richter), I came into this book with zero knowledge of COM and the MFC (I'm from the Unix world). Knowing MFC and COM would help immensely, I was still able to get my C++ database up and running within about four hours with this book.

   I'd prefer a revised version that tosses out the MFC and instead does I/O with iostreams. If you can filter the MFC stuff out, the basic information seems to be there, and the book paid for itself on it's first day.




5. I had a really hard time obtaining this book. For some reason, the publisher seems to have stopped printing it. The most recent edition was printed in 1999, so it is not that old. It really is a wonderful book. It does what I need most from a programming book - it explains a concept and then walks you through how to do it step by step. The book is extremely hands-on. After much searching, I was finally able to locate the book by means of an online used/out of print bookstore.

   Another thing I like about the book is that it uses Access as the database for all of the exercises. While SQL Server is important to learn, using it introduces another set of connection problems that you don't get with Access. I liked being able to learn the C++ database concepts without that extra level of headache.

   The book covers all the major database topics in a way that is thorough and easy to understand. And most importantly, it shows you how to actually use the stuff. It is worth the struggle to obtain it.

5 comments about Building Financial Derivatives Applications with C++:.

1. If you have shopped around you may be aware that this is one of the only books available that is dedicated to pricing derivatives using C++. Perhaps like me as a student of Pure and Applied Mathematics you have wondered why all those Financial Engineering grad schools are pushing so hard for C++.
   You can expect that this book will introduce you to a set of traditional algorithms for option pricing at a basic level. It will be helpful if you already know standard C++, and also if you have seen mathematical models of what is being implemented here.
   



2. This book has the contents that a graduate student will look for in a course that covers derivatives application development using C++. Dr. Brooks book is by far the best I have ever scanned for the purpose of finance. For a quant analyst position it is important to understand how to generate various mathematical tools using C++ and the book covers such code in details. The book covers Lattice based solutions through extensive coding of Black Derman and Toy, Monte Carlo simulation, curve fitting techniques and iterative numerical solutions technique .The most attractive part of this book is the simplistic approach to mathematical complexities and Dr. Brooks excels in handling the mathematics and the language. His examples are in Borland C++ so VC or other C users need not be intimidated as the basic C++ principles are the same for any type of proprietary C++ language. In fact Borland is a good way to get introduced to the visual C++ modeling approach at the graduate level, it definitely reduces the entry barrier into coding.



3. One of the best books in the market. I enjoyed reading it.



4. This is very accessible book to learn from. If really want be a quanta this is the book to start with. All quantas entering the field of financial derivatives should start with this book, which includes all you will need to know to program and implement your first derivatives' modeling application.



5. This is one of the worst-written programming books I have seen yet. I'm sorry I bought it. It appears to be written by a man who knows quite a bit about finance, and dangerously little about C++ programming. Duffy's review correctly describes the main flaws.
   
   I would add that (1) The book is not structured to build upon OO, GOF Patterns, or STL design principles; (2) The code does not follow even basic C++ coding conventions; (3) The images (screenshots) are agonizingly UNREADABLE; (4) The code listings are in ITALICS using a variable-pitch font [is COURIER font code listing so difficult to include in a $100 book???]; (5) No over-arching component object model is suggested ANYWHERE in the book.
   
   Some of the efforts at brevity are just plain WRONG or even DANGEROUSLY WRONG to teach beginning programmers. For example, Pg 19 Data Types section:
   
   ----------------
   int - holds integer numbers up to a little over 2 million, for example, "int I = 2000000;."
   long - same as int.
   ----------------
   
   WRONG, PROFESSOR! This is not only a syntactically incorrect example, but a just plain wrong assertion. If the reader does not know how to determine the (platform-specific) size of an "int" or "long", then the author has only served to confuse the matter further!
   
   Furthermore, I consider it a "cheapskate" tactic to ask readers to pay for the code from this book in electronic form (particularly when the book's code listings are so sloppy). That said, I would not use the code, even if it had been supplied for free ... but it *might* have been interesting to have something to play around with...
   
   Have any of the reviewers actually USED any code from this book without substantial refactoring?
   
   The only use I could see for this book is for intermediate-advanced fin-techs, who want to review a few general algorithms for selected derivative calculations (futures, forwards, etc) ... but just be prepared to squint and suffer through reading the code!

No comments about Artificial Intelligence Using C.

5 comments about C++ For Game Programmers (Game Development Series).

1. Going through the contents and skimming through, I'm not sure how this book in any way relates to game programming. It could be a great C++ book, but that's not what the title is about. Some of the things it is suggesting break established paradigms of game developement. It *may* help Windows based game programmers, but it sure doesn't cover any of the myriad of issue sin using C++ on a console such as the PS2, GameCube, etc....
   
   It seems like another C++ book. Any thoughts on this?



2. This is indeed a good book. It gives you almost every important tips you ever need to know. After reading this book, if you're able to catch/grasp what the author is trying to convey, I'm sure that you'll have a few level-ups in your C++ skills.
   
   Although it stated for Game Programmers in the title, the tips and tricks can be applied to other application programming using C++ too.
   
   However, if you are looking for design patterns, this is not the book. It doesn't touch anything about design pattern as this is totally out of the scope.
   
   Also, if you are newbie in C++, perhaps you would like to read other C++ book first.



3. First off, the guy who said this book has nothing to do with game programming is wrong. He was obviously expecting a "read this book and make a Doom clone in 4 hours" book. There is no book like that, and this book did not advertise that.
   Like the title of my review suggests, there is more to game programming than graphics. This book teaches no graphics; it does, however, teach you to use graphics wisely. Also, it doesn't teach C++ from the beginning - you are expected to know C++ before reading this book. What this book does is teach you to use C++ effectively in game programming.
   Overall, this is a good read for anyone interested in making high quality games.



4. While focusing on game development challenges, this book provides excellent advice on designing c++ applications. The author demonstrates possible implementations comparing their strengths/tradeoffs and gives very useful advice on solving common problems in game architecture.
   The book is not code intensive (all examples are available in the CD-ROM), and should be useful to any intermediate c++ programmer, especially the ones planning to develop games.



5. As other reviewers have said this book isn't really a game programming book. It's title really ought to be "C++ programming for high performance applications". That said it is a wonderful book! I highly recommend it as a well written, easy to read intermediate/advanced C++ book.

5 comments about C for Dummies, Volume 1.

1. I'm a 2nd year computer science major and we use K&R (The C Programming Language 2nd Edition ANSI version) in class. I find it incredibly dry and boring, although I suppose it's terse and to the point. C for Dummies can be repetitious at times but I find that I need and appreciate that. And yeah, the quizzes are dumb but who's taking them anyway? I get enough in class. :) The sections on pointers or structures alone are well worth the price of admission. The index is especially well done. It's easy to jump around, scan and use the book as a reference guide. I also like the "cheat sheet" containing hints and tips that you can rip out and keep by your computer.
   SIDE NOTES: Even as a neophyte programmer, I was able to jump pretty much straight into Vol. 2, having only a year of Java experience previously. Also, we use unix gcc at the university and Gookin uses Borland C++ and Microsoft Visual C++ to compile. An earlier reviewer seemed to think that excluding gcc was wrong but I don't think it makes much of a difference -- the fundamental concepts and implementations are the same. The header files Gookin uses are the same as the ones we use in class with unix, too. All in all, Gookin's Vol. 2 is a great book. I haven't looked at Vol. 1 at all but I have no regrets buying the 2-volume set.



2. This book was a complete waste of time for me. It barely teaches you anything after reading the first volume. What took 1000 pages in this book I can learn in in 100 pages of another book. The author uses so much humor in this book that it gets extremely frustrating. For example, in the quizes after each section he gives a question with multiple choice answers. There are amazingly stupid answers to choose from leaving you with only one logical answer. He might as well just give you the answer rather than writing down bs. He repeats each example over and over again which makes it frustrating. I found myself repeating the same things withouth learning anything new. The only time I would recommend this book if you were some moron who has an iq of 90 and can barely read or if you're a 10 year old and doesn't know what you're doing. It's ridiculous how simple it is he teaches you. It takes the author 20 pages to teach you something you can easily learn in anotehr book in 1 page. I recommend C Primer Plus by Stephen Prata rather than this piece of garbage.



3. I got this book back in 1998 but had no time to learn it until 2004 fall. -.-'
   
   I had covered vol 1 and is reading vol 2 now and had browsed over the 2nd edition and the all-in-one companion in Borders. The comments are made after my browsing on ALL 3 BOOKS.
   
   Gookin has a way to teach newbies on "hard stuff" but there are good and bad about the book:-
   
   1. Readablity:
   
   The good:- Fun and easy. Definitely a good book for those that feels programming is hard and boring. Dan makes it really enjoyable.
   
   The bad:- Too drag and like some of the reviews had said, waste of time when something that could be explain in 1 page he used 6-8 pages (and more in some topics) to talk it out. Beginners != Idiots.
   
   2. Assumption:
   Not good but not very bad either... below satisfatory?:- The author had over assuming about the reader. The book stated that it is a beginner to intermediate level book. When I first open the book, I realised that I have to have a C/C++ compiler readily installed in the computer. Damn! I wouldn't know what a C/C++ compiler if I am a total noob! I ended up spending time finding out what is a compiler and where to get one before I really start learning from the book.
   
   I suggest that a section be devoted to telling where to get a C/C++ compiler will be good. I am currently using Bloodshed's Dev-C++ compiler for Windows. I am learning Linux now and naturely it comes with a C/C++ compiler.
   
   3. Coverage on different Operating Systems:
   Bad:- It covers programming in DOS prompt only. Forget about programming in Windows environment, Mac, UNIX and Linux. I got to know how to compile the source codes in Linux in another C programming book (don't bother to ask about that book. That sucks even more!).
   
   Perhaps Dan was devoted to focus on teaching C only but the truth is that some of the examples (those that called for BIOS functions) could not be compile in WinXP environment. I tried on Linux but in Linux, it does not have conio.h and linux.h file. So then again, what are the alternative header files are we going to use if we are Linux O/S users?
   
   Even if Dan is limited by the pages he is allocated to write the book or by whatsoever limitation for not explaining C programming for Windows. I think an introductory lesson should be taught and then recommand the users to read more by buying other books on Win Programming. He did the latter but flopped the formal.
   
   I am currently at a bottle neck of my learning of C due to the BIOS function thing and have to get another book on programming C for windows to continue my learning on C. Kind of suck! I hope I can find a good book. -.-'



4. C for dummies was the first book I purchased (several years ago) to teach myself something about programming a computer. Dan Gookin is a great writer and he even took the time to help with some questions via email as I went through the book.
   
   This book is light weight in tone but a solid heavy weight in content and is a fun read. But don't underestimate this book. If you want to know the basics and have a sold understanding of the basics then this is the book for you. One of the most important things a beginning book must have is lots of "fully coded" examples. Many books will give you a snip-it of code that does't help a beginning programmer. It was great fun, I learned alot and what I learned from Dan Gookin I was able to apply towards learning C++ and Visual Basic.
   
   I would suggest working through this book, practice practice and practice some more. The key is to apply yourself. I worked every project and even combined them. Adding my own twists here and there to make up my own little programs as I worked through this book. When you finish, start working through C for Dummies 2 as it picks up right where the first book ends. Sadly, I had to wait for the second book to be written!! It was worth the wait.
   
   It is all about the desire to learn, no matter how great a book is, without the desire to apply yourself you will not learn. Dan helps break down the resistance barrier and you will find yourself laughing and learning and wanting to learn more the Wambooli way.
   
   I enjoyed this book. I passed it on to my teenager for his first programming book. This book is great for learning the fundamentals of progamming and believe me they apply to all programming languages.



5. Dan Gookin makes learning C fun & easy with a bunch of humor. This book is STRONGLY recommended for professionals & beginners. You haven't read a book about C until you've read 'C for Dummies'.

5 comments about Perl: The Complete Reference.

1. I actually found this book in a bookstore while looking for Programming Perl. This book has an excellent reference section, with in-depth descriptions on everything. It is very well formatted. I don't know how good it is to learn from, but if you want a quick lookup reference this book is for you. Programming Perl provides the same information, but costs about $50.



2. Apparently, this book is not for beginners. You will get lost if you try to learn perl by yourself. It may be a good reference book, I think, after I read the exhaustive listing of I/O variations.



3. I felt this book fell into the trap that many teaching books fall into - it assumes that the reader is at the same level as the author.

   Don't get me wrong, it was a *very* useful book, but it could have been a lot clearer about many of the key issues.

   For a beginner - don't buy this book. For an "advanced beginner", do =D




4. 
   This book is an outstanding Perl REFERENCE.
   
   It's perfect for those times when you need something done in Perl but can't recall the syntax, semantics or parameters of some construct or function, or just when looking for a way to do something. I use it daily when writing in Perl, preferring it over perldoc and half a bookshelf of other Perl books that I have access to - it's that much better.
   
   It's not a "tutorial", though, and it's not "for dummies". While you can certainly learn Perl from scratch using just this volume, I would advise against that if you're a TOTAL programming beginner. There are better "tutorial" books out there, get one of those and then get this as a reference. If you're a programmer already proficient in some other language, you won't have much of a problem switching to Perl using just this book.
   
   Pros :
   * it's very readable
   * goes into considerable detail - mind the page count!
   * the explanations are to the point - no useless stories or "cute" stuff
   * summary tables are there when they ought to be - easy on the eyes
   * it has a very comprehensive index - a must for a reference
   * it's original content - not a perldoc rehash like some other books
   * for each function there's an additional short summary including scalar/list context return values (love that one!).
   
   Cons :
   * it's... big. physically. not very convenient - but the content is well worth it!
   * it's slightly dated (it covers Perl 5.6) but that hardly shows as of 5.8
   * the more serious problem is that of availability - you can hardly find this book in stores nowadays, no idea why.
   
   In a word, if you're shopping for a Perl reference - this is the book to get.



5. Terrible book for learning Perl. As an example, I needed to know how to add an element to the end of an array. So I went to the 'Variables and Data' chapter where there is a section on arrays. Well, it mentions how to create an array, how to change the value of a specific array position and thats about it. I had to search online to find out how to do a very basic thing--add to the end of an array. The 'Variables and Data' section makes no mention of using 'push(@array, "whatever")'. I keep having to search online for very basic things that should be easily found in this book. Oh, and starting the book by talking in-depth about 'Perl parsing rules'--I got confused from the start. Definitely not something you want to learn Perl with.

2 comments about C# Essentials (Prentice Hall Ptr Microsoft Technologies Series).

1. My boy friend at UCLA let me borrow this book, but I finally bought my own copy. This book covers all of the features of C# which is the new Microsoft language.

   If you know any C++, you are going to have no trouble with C# espically with this book. They have included a lot of short example programs that help you understand C# programming features.

   They really helped me understand arrays in C# because they are totally different than for C++. Also, get ready for this, pointers are not used in C#, so you have got to do things another way. If you are like me, I didn't get along to well with pointers anyway.

   Get the book, dude.




2. This is exactly what I was looking for, a book that examines the nuts and bolts of the C# while taking advatage of my C foundation. The book also makes language comparisons to Visual Basic, C/C++, Java, JScript, and Visual Foxpro. I thoroughly enjoyed the historical chapter 1, describing the evolution of programming. General programming concepts like proper use of control flow selection, proper initialization, and passing by reference versus passing by value are covered sufficiently and efficiently. C# language features are made clear with example code. The debugging environment in .NET was also covered, explaining the whole set of menu options for debugging.
   You are not going to get any programs of that put together all the concepts, but your going to build the foundation to taking that step on your own. The authors are remarkably clear and to the point, usually giving an example where necessary. I'll be interested to try their C# for Windows Programming book next. A final comment: this is not a reference book, it more of an "adapting to C#" type of book, which serves its purpose to the tee.