Where can I find errata lists for the printed books (particularly NR in C, 2nd Ed.)? The Cambridge University Press site (uk.cambridge.org/computerscience/recipes/question.htm (http://uk.cambridge.org/computerscience/recipes/question.htm) ) tells me that errata for the printed books are posted on www.nr.com, but I can't find them here.

Thanks.

Ah, you've hit on a sore subject! We've always felt it important to keep track of all changes in the code (as documented in the Upgrade section of the web site, http://www.nr.com/upgrade/upgrade-info.html
especially in the text patch files).

But we haven't been consistent in keeping track of the various small changes in the text that get made with each reprinting. So, regrettably, there is no master list of errata.

However, this is not as bad as it seems: Most people who need errata want to know whether a specific place (maybe something seeming questionable) has been changed from their printed copy. The easy way to find this out is to check it against the Books On-Line resource, available at http://www.nr.com/nronline_switcher.html . This is generally the most current reprint version.

(Confession: Right now the Books On-Line resource is at version 2.08, but we expect it to be upgraded to the new version 2.10 -- just out -- within a month or two.)

Hope this helps.

Thanks. I am sorry that there are not errata for the printed version, but your suggestion to look at the on-line book is quite helpful.

As you guessed, when I want to know about errata, it's with regard to a few particular sections and checking out the on-line version suffices nicely.

I have the Fortran books -- vol 1 (version 2.10) and vol 2 (version 2.06) -- and would like to bring vol 2 up to date (to version 2.10) -- although I really should have ensured it was the latest version when I bought it! I was wondering whether there is a list, similar to that given at http://www.nr.com/latest-known-bugs.html, but for bugs relating to version 2.06 -- so that I can make the necessary changes to vol 2 (version 2.06 ==> 2.08 ==> 2.10).

Thanks,
Tom

Tom, I assume that what you are really concerned with is updating the Fortran 90 code, not the text.

I think the best way to do this is using the Unix-style patch files. You can find these in general through the Upgrades link on the home page. For your particular case of updating Fortran 90 from 2.06 to 2.10, the file
http://www.nr.com/upgrade/208/U9F206b08.txt
takes you from 2.06 to 2.08, and the file
http://www.nr.com/upgrade/upg210patch/U208210f-90.txt
takes you from 2.08 to 2.10.

Hope this helps!

no, i'm actually concerned about updating the text. what i want to do is to make a note in the book where revisions have been made (by versions 2.08 and 2.10) -- so that anyone looking at my book knows to also check the pdf's for revisions.

if this revision list (for 2.08) is unavailable, i understand and can live without it -- i'm just being somewhat pedantic. (note: my fortran code is up to date.)

Oh, sorry. But, as explained above, this is just not something that we have tracked. So, not available.

Bill P.

dont think i've made myself clear about what i'm looking for. i know you have said that you dont keep a list of all the various small changes made in the text (i'm not worried about these), but you do keep a list of bugs http://www.nr.com/latest-known-bugs.html -- these bugs are the ones that i am concerned about and would like to correct in the text (or to make a note that there is a bug there).

currently, lastest-known-bugs.html gives a list of bugs found in versions 2.10 and 2.08 -- i was after a "latest-known-bugs.html for version 2.06" (if available).

thanks, tom.

Hi, Tom. "Latest known bugs" means just that -- a list that accumulates between reprintings. When the time for a reprinting comes around, we typically do some additional scrutinizing, resulting in a bunch of things being fixed that may go beyond what is in "latest known bugs". We may not be consistent in updating the "latest known bugs" list at that point; rather we update the book page files directly (and of course the code files).

So, I still think that the only way to flag the pages on which there are code bugs is to flag the pages that have code that is corrected in the Unix patch files previously mentioned. The patch files are the *only* definitive list of fixed bugs in a new reprinting.

Cheers,
Bill P.

ok, sweet -- looks like i might have to set aside an hour or so and go thru the patch files. thanks for the info.