How well might the C++ Without Fear book help me to deal with a project that uses a very proprietary (IBM) version of C/C++ in which the code is intertwined with DB2-specific SQL prepared statements (*.sqC files)?
David, I guess the book does not deal with what you are asking...it focuses on the new standard C++0x. In the table of contents I did not find anything specific to IBM C++. BTW, why don't you tell us more about the challenges a programmer faces in the DB2 embedded SQL stmts in C/C++? Will be interested to hear from the practitioner!
Java Pal - Your friend in technology and innovation...India.
What I am getting from reading the posts here is that this is a intro book of C++ for someone new to programming. Like David said, its focuses on standard C++, mostly BASIC standard of C++. Thus, I don't think it would matter much if it uses proprietary IBM version of C/C++ or not.
Hi. Brian Overland here. Yes, one thing you have to deal with when writing a C++ book is that you cannot know which specific implementation or even which specific version the thousands of readers out there might have. I wrote C++ Without Fear to try to cover as many versions of C++ as possible. Fortunately, it has mostly been very standardized.
One of my problems, in fact, has been how up-to-date to make the version of C++ I am working with. For example, in the first edition, in my early drafts I was avoiding using some of the slicker features of C++... new-style type casts for example. But for the second edition, I updated the book with the idea in mind that certain things are now very standard. Even "long long int" -- considered part of the newest standard -- has long been standard for most compilers.
But no, the book has nothing specific to IBM. You'll need to get IBM's documentation on that.
-- Brian O.
Joined: Mar 14, 2007
Right, well I suppose I was being a little too optimistic to think that this book would solve world peace, but one can hope eh?
As to my current challenges, imagine being handed a C++ project where the code is so proprietary that it is nearly unrecognizable as C/C++, and to add to this, the code is heavily steeped in database SQL statements (also proprietary) which bind to a proprietary database on a proprietary server. OK, so what? Now imagine learning that the development IDE is basically vi (or a text editor). There is not even a command line debugger to speak of, and all of the development must be done on this remote server due to the data binding to the database!
So now imagine that you haven't really done much of anything with C/C++ in over 12 years, and the experience you had with C/C++ was that of a completely different proprietary vendor whose code implementation was also anything but standard.
Someone mentioned "long long int" - when I saw this, I thought it must be a typo or something! OK, so it sounds like I could at least use the book to learn what C/C++ is supposed to look like, as well as what strange things like "long long int" are - as I continue my nightmarish adventure.