Giant C++ resources list, 3rd edition

**Mike Tyndall** · Jul 22 '05, 06:33 PM

Re: Giant C++ resources list, 3rd edition

> -Books added:[color=blue]
> C++ Coding Standards (Required Reading - upcoming)
> Memory as a Programming Concept in C and C++
> Scientific and Engineering C++
> Writing Secure Code: 2nd Edition[/color]

Dagnabbit! I never added these to the list. Here's what it would look like:

**REQUIRED READING**
C++ Coding Standards (Sutter & Alexandrescu)

**OTHER C++ BOOKS**
Memory as a Programming Concept in C and C++ (Frantisek Franek)
Scientific and Engineering C++ (Barton & Nackman)
Writing Secure Code: 2nd Edition (Howard & Leblanc)

Next time I'll wait a little while before posting :)

//mike tyndall

**Mike Tyndall** · Jul 22 '05, 06:33 PM

Re: Giant C++ resources list, 3rd edition

> Function pointer tutorials - www.functionpointer.org

Yet another small fix. This should be www.function-pointer.org

//mike tyndall

**Steven T. Hatton** · Jul 22 '05, 06:33 PM

Re: Giant C++ resources list, 3rd edition

Mike Tyndall wrote:
[color=blue][color=green]
>> Function pointer tutorials - www.functionpointer.org[/color]
>
> Yet another small fix. This should be www.function-pointer.org
>
> //mike tyndall[/color]

Interestingly I have most of the books on your required reading list, and
the only C++ books I have that didn't make the list are either antiquated,
such as the C++ARM, Ira Pohl's first edition, and Horstmann's first
edition, or quite respectable in their own right, for example Lippman's
"Inside the C++ Object Model, or the O'Reilly "C++ Pocket Reference". The
only two books I've read extensively thus far are TC++PL(SE), and the
Pocket Reference.

But I am really replying to your message to make an observation about
function pointer, and particularly the examples presented on the link you
provided. I've been seriously considering using a very similar approach to
passing events that deal with propagating state changes. I plan of filling
the array(or vector) of function pointers with functors containing the
propagating data, as well as the means to invoke the modifier functions on
the listener. I haven't weighed the pros and cons of this very closely, so
it's hard to say how well it will work in practice.
--
"[M]y dislike for the preprocessor is well known. Cpp is essential in C
programming, and still important in conventional C++ implementations , but
it is a hack, and so are most of the techniques that rely on it. ...I think
the time has come to be serious about macro-free C++ programming." - B. S.

**John Harrison** · Jul 22 '05, 06:34 PM

Re: Giant C++ resources list, 3rd edition

>[color=blue]
> All books are available on Amazon and probably on eBay. Please reply to
> this message if you feel it could be improved in any way (removing books,
> adding books, recommending books, general suggestions, etc.).
>
> Remember, please feel free to criticize any part of this list or offer
> suggestions.
>[/color]

In the general programming section how about adding the 'wizard book',
Structure and Interpretation of Computer Programs by Abelson and Sussman.
Any C++ programmer who reads this will get a feel for a style of programming
that is completely different from normal C++ styles, which is no bad thing.

Probably the best general programming book I have ever read.

john

**Mike Tyndall** · Jul 22 '05, 06:34 PM

Re: Giant C++ resources list, 3rd edition

"John Harrison" <john_andronicu s@hotmail.com> wrote in message
news:2pqj4fFnuq 2iU1@uni-berlin.de...[color=blue][color=green]
> > All books are available on Amazon and probably on eBay. Please reply to
> > this message if you feel it could be improved in any way (removing[/color][/color]
books,[color=blue][color=green]
> > adding books, recommending books, general suggestions, etc.).
> >
> > Remember, please feel free to criticize any part of this list or offer
> > suggestions.[/color]
>
> In the general programming section how about adding the 'wizard book',
> Structure and Interpretation of Computer Programs by Abelson and Sussman.
> Any C++ programmer who reads this will get a feel for a style of[/color]
programming[color=blue]
> that is completely different from normal C++ styles, which is no bad[/color]
thing.[color=blue]
>
> Probably the best general programming book I have ever read.[/color]

Sounds good! I'll add it next time.

//mike tyndall

**David Hilsee** · Jul 22 '05, 06:35 PM

Re: Giant C++ resources list, 3rd edition

"Steven T. Hatton" <susudata@setid ava.kushan.aa> wrote in message
news:1q6dnbXOGu wxjqXcRVn-tA@speakeasy.ne t...
<snip>[color=blue]
> But I am really replying to your message to make an observation about
> function pointer, and particularly the examples presented on the link you
> provided. I've been seriously considering using a very similar approach[/color]
to[color=blue]
> passing events that deal with propagating state changes. I plan of[/color]
filling[color=blue]
> the array(or vector) of function pointers with functors containing the
> propagating data, as well as the means to invoke the modifier functions on
> the listener. I haven't weighed the pros and cons of this very closely,[/color]
so[color=blue]
> it's hard to say how well it will work in practice.[/color]

Are you using something like Loki's Functor?

--
David Hilsee

**apm** · Jul 22 '05, 07:37 PM

Re: Giant C++ resources list, 3rd edition

"Mike Tyndall" <Mike_Tyndall_1 @hotmail.com> wrote in message news:<qZidnayHX 6QrBKrcRVn-qQ@comcast.com> ...[color=blue]
> Sorry I'm late, everybody! I'll try to post it nearer the start of the month
> next time.
> **OTHER C++ BOOKS**
> Industrial Strength C++ Rules and Recommendations (Henricson & Nyquist)[/color]

FYI this book is out of print and AFAIK it is not going to be
reprinted, despite the demand. The authors have made the book
available as a PDF download from
http://hem.passagen.se/erinyq/industrial.

Regards,

Andrew Marlow

**Mike Tyndall** · Jul 22 '05, 07:37 PM

Re: Giant C++ resources list, 3rd edition

> > Sorry I'm late, everybody! I'll try to post it nearer the start of the
month[color=blue][color=green]
> > next time.
> > **OTHER C++ BOOKS**
> > Industrial Strength C++ Rules and Recommendations (Henricson & Nyquist)[/color]
>
> FYI this book is out of print and AFAIK it is not going to be
> reprinted, despite the demand. The authors have made the book
> available as a PDF download from
> http://hem.passagen.se/erinyq/industrial.[/color]

Thanks for the info. I'll put it with the Thinking in C++ books on the list
next time.

//mike tyndall

**Ioannis Vranos** · Jul 22 '05, 07:37 PM

Re: Giant C++ resources list, 3rd edition

apm wrote:
[color=blue]
> FYI this book is out of print and AFAIK it is not going to be
> reprinted, despite the demand. The authors have made the book
> available as a PDF download from
> http://hem.passagen.se/erinyq/industrial.[/color]

Looks great, however then I checked the publishing date and it is 1997.
Then I wondered how much C++98 compliant could be, and searched for the
word iostream. And unfortunately it is iostream.h.

--
Ioannis Vranos

IIS 7.5 Detailed Error - 404.0 - Not Found

http://www23.brinkster.com/noicys

**Mike Tyndall** · Jul 22 '05, 07:37 PM

Re: Giant C++ resources list, 3rd edition

> > FYI this book is out of print and AFAIK it is not going to be[color=blue][color=green]
> > reprinted, despite the demand. The authors have made the book
> > available as a PDF download from
> > http://hem.passagen.se/erinyq/industrial.[/color]
>
> Looks great, however then I checked the publishing date and it is 1997.
> Then I wondered how much C++98 compliant could be, and searched for the
> word iostream. And unfortunately it is iostream.h.[/color]

Obviously that's a problem, but the book's still good, right? I could just
note on the list that it's best not to read it until you have some
experience.

//mike tyndall

**Gregg** · Jul 22 '05, 07:37 PM

Re: Giant C++ resources list, 3rd edition

"Mike Tyndall" <Mike_Tyndall_1 @hotmail.com> wrote in
news:19GdnXEEs7 SSvs_cRVn-vw@comcast.com:
[color=blue][color=green][color=darkred]
>> > FYI this book is out of print and AFAIK it is not going to be
>> > reprinted, despite the demand. The authors have made the book
>> > available as a PDF download from
>> > http://hem.passagen.se/erinyq/industrial.[/color]
>>
>> Looks great, however then I checked the publishing date and it is
>> 1997. Then I wondered how much C++98 compliant could be, and searched
>> for the word iostream. And unfortunately it is iostream.h.[/color]
>
> Obviously that's a problem, but the book's still good, right? I could
> just note on the list that it's best not to read it until you have
> some experience.
>
> //mike tyndall[/color]

Some of its recommendations differ from those of other well-regarded
books. For example, recommendation 11.2, "Remove all assertions from
production code". I just got finished reading in "The Pragmatic
Programmer", Hunt and Thomas, that I should leave assertions turned on
(page 123), and that they should be disabled only for performance
reasons. In fact, a particular usage of assertive programming called
design by contract is recommended by them.

Gregg

**Ioannis Vranos** · Jul 22 '05, 07:37 PM

Re: Giant C++ resources list, 3rd edition

Gregg wrote:
[color=blue]
> Some of its recommendations differ from those of other well-regarded
> books. For example, recommendation 11.2, "Remove all assertions from
> production code". I just got finished reading in "The Pragmatic
> Programmer", Hunt and Thomas, that I should leave assertions turned on
> (page 123), and that they should be disabled only for performance
> reasons. In fact, a particular usage of assertive programming called
> design by contract is recommended by them.[/color]

Well in theory, in production code assert() should be disabled since it
doesn't provide anything to the end user other than redundant logical
checks not needed in production code.

For run-time error handling use exceptions.

--
Ioannis Vranos

IIS 7.5 Detailed Error - 404.0 - Not Found

http://www23.brinkster.com/noicys

**Gregg** · Jul 22 '05, 07:37 PM

Re: Giant C++ resources list, 3rd edition

Ioannis Vranos <ivr@guesswh.at .grad.com> wrote in news:citcfo$1re e$1
@ulysses.noc.nt ua.gr:
[color=blue]
> Gregg wrote:
>[color=green]
>> Some of its recommendations differ from those of other well-regarded
>> books. For example, recommendation 11.2, "Remove all assertions from
>> production code". I just got finished reading in "The Pragmatic
>> Programmer", Hunt and Thomas, that I should leave assertions turned on
>> (page 123), and that they should be disabled only for performance
>> reasons. In fact, a particular usage of assertive programming called
>> design by contract is recommended by them.[/color]
>
> Well in theory, in production code assert() should be disabled since it
> doesn't provide anything to the end user other than redundant logical
> checks not needed in production code.[/color]

That assumes you are shipping bug-free code. What it provides to the end
user is code that does not keep running after it has entered a state in
which it should have stopped, thereby risking corrupting the user's data.
It also provides the ability to provide feedback that can help provide
the user with bug fixes.
[color=blue]
> For run-time error handling use exceptions.[/color]

Depends on what kind of run-time error, how you want to handle it, and
whether the system can produce a stack trace in the case of an unhandled
exception.

Also, assertions do not have to be macros. THey can be implemented as
exceptions. I believe Stroustrup has a template example of this in C++
Programming Language book.

Gregg

Giant C++ resources list, 3rd edition

Giant C++ resources list, 3rd edition

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment