Skip to content

Commit

Permalink
Cleanup, fix dead links
Browse files Browse the repository at this point in the history
  • Loading branch information
richelbilderbeek committed Mar 3, 2018
1 parent c1550b7 commit 031b18f
Show file tree
Hide file tree
Showing 16 changed files with 1,221 additions and 1,878 deletions.
2 changes: 1 addition & 1 deletion content/CppConst.md
Expand Up @@ -56,7 +56,7 @@ In [class design](CppClassDesign.md) consider using:
* [6] [Herb Sutter](CppHerbSutter.md), [Andrei Alexandrescu](CppAndreiAlexandrescu.md). C++ coding standards: 101 rules, guidelines, and best practices. ISBN: 0-32-111358-6. Item 15: 'Use const proactively'.
* [7] [Herb Sutter](CppHerbSutter.md). Exceptional C++ style. 2005. ISBN: 0-201-76042-8. Item 1 guideline: 'Be const correct'.
* [8] [Marshall Cline](CppMarshallCline.md), [Greg Lomow](CppGregLomow.md) and [Mike Girou](CppMikeGirou.md). C++ FAQs. ISBN: 0-201-3098301. FAQ 14.05: 'Is const correctness tedious?' (Answer: no).
* [9] [The C++ FAQ Lite](http://www.parashift.com/c++-faq-lite/const-correctness.html#faq-18.1). Item 18.1: What is 'const correctness' (Answer: 'A good thing')?
* [9] [The C++ FAQ Lite](https://isocpp.org/wiki/faq/const-correctness#overview-const). Item 18.1: What is 'const correctness' (Answer: 'A good thing')?
* [10] [Bruce Eckel](CppBruceEckel.md). Thinking in C++, second edition, volume 1. 2000. ISBN: 0-13-979809-9. Item 8: 'Constants', paragraph 'Summary': 'const-correctness can be a lifesaver for projects'.
* [11] [John Lakos](CppJohnLakos.md). Large-Scale C++ Software Design. 1996. ISBN: 0-201-63362-0. Chapter 2.3.3
* [12] [John Lakos](CppJohnLakos.md). Large-Scale C++ Software Design. 1996. ISBN: 0-201-63362-0. Chapter 9.1.6: 'Every object in a system should be const-correct'
Expand Down
46 changes: 11 additions & 35 deletions content/CppConstCorrect.md
Expand Up @@ -11,38 +11,14 @@ correct](CppConstCorrect.md) \[7-11\].

## [References](CppReferences.md)

1. [Bjarne Stroustrup](CppBjarneStroustrup.md). The C++ Programming
Language (3rd edition). ISBN: 0-201-88954-4 7.9.3: 'Use const
extensively and consistently'.
2. [Scott Meyers](CppScottMeyers.md). Effective C++ (3rd
edition).ISBN: 0-321-33487-6. Item 3: 'Use const whenever possible'.
3. [Jarrod Hollingworth](CppJarrodHollingworth.md), [Bob
Swart](CppBobSwart.md), [Mark Cashman](CppMarkCashman.md), [Paul
Gustavson](CppPaulGustavson.md). Sams C++ Builder 6
Developer's Guide. ISBN: 0-672-32480-6. Chapter 3: 'Understand and
use const in your code'.
4. [Jesse Liberty](CppJesseLiberty.md). Sams teach yourself C++ in
24 hours. ISBN: 0-672-32224-2. Hour 8, chapter 'Const member
functions': 'Use const whenever possible.'.
5. [Scott Meyers](CppScottMeyers.md). Effective C++ (3rd edition).
ISBN: 0-321-33487-6. Item 2: 'Prefer consts, enums and inlines
to \#defines'.
6. [Herb Sutter](CppHerbSutter.md), [Andrei
Alexandrescu](CppAndreiAlexandrescu.md). C++ coding standards: 101
rules, guidelines, and best practices. ISBN: 0-32-111358-6. Item 15:
'Use const proactively'.
7. [Herb Sutter](CppHerbSutter.md). Exceptional C++ style. 2005.
ISBN: 0-201-76042-8. Item 1 guideline: 'Be const correct'.
8. [Marshall Cline](CppMarshallCline.md), [Greg
Lomow](CppGregLomow.md) and [Mike Girou](CppMikeGirou.md).
C++ FAQs. ISBN: 0-201-3098301. FAQ 14.05: 'Is const correctness
tedious?' (Answer: no).
9. [The C++ FAQ
Lite](http://www.parashift.com/c++-faq-lite/const-correctness.html#faq-18.1).
Item 18.1: What is 'const correctness' (Answer: 'A good thing')?
10. [Bruce Eckel](CppBruceEckel.md). Thinking in C++, second edition,
volume 1. 2000. ISBN: 0-13-979809-9. Item 8: 'Constants', paragraph
'Summary': 'const-correctness can be a lifesaver for projects'.
11. [John Lakos](CppJohnLakos.md). Large-Scale C++ Software Design.
1996. ISBN: 0-201-63362-0. Chapter 9.1.6: 'Every object in a system
should be const-correct'
1. [Bjarne Stroustrup](CppBjarneStroustrup.md). The C++ Programming Language (3rd edition). ISBN: 0-201-88954-4 7.9.3: 'Use const extensively and consistently'.
2. [Scott Meyers](CppScottMeyers.md). Effective C++ (3rd edition).ISBN: 0-321-33487-6. Item 3: 'Use const whenever possible'.
3. [Jarrod Hollingworth](CppJarrodHollingworth.md), [Bob Swart](CppBobSwart.md), [Mark Cashman](CppMarkCashman.md), [Paul Gustavson](CppPaulGustavson.md). Sams C++ Builder 6 Developer's Guide. ISBN: 0-672-32480-6. Chapter 3: 'Understand and use const in your code'.
4. [Jesse Liberty](CppJesseLiberty.md). Sams teach yourself C++ in 24 hours. ISBN: 0-672-32224-2. Hour 8, chapter 'Const member functions': 'Use const whenever possible.'.
5. [Scott Meyers](CppScottMeyers.md). Effective C++ (3rd edition). ISBN: 0-321-33487-6. Item 2: 'Prefer consts, enums and inlines to \#defines'.
6. [Herb Sutter](CppHerbSutter.md), [Andrei Alexandrescu](CppAndreiAlexandrescu.md). C++ coding standards: 101 rules, guidelines, and best practices. ISBN: 0-32-111358-6. Item 15: 'Use const proactively'.
7. [Herb Sutter](CppHerbSutter.md). Exceptional C++ style. 2005. ISBN: 0-201-76042-8. Item 1 guideline: 'Be const correct'.
8. [Marshall Cline](CppMarshallCline.md), [Greg Lomow](CppGregLomow.md) and [Mike Girou](CppMikeGirou.md). C++ FAQs. ISBN: 0-201-3098301. FAQ 14.05: 'Is const correctness tedious?' (Answer: no).
9. [The C++ FAQ Lite](https://isocpp.org/wiki/faq/const-correctness#overview-const). Item 18.1: What is 'const correctness' (Answer: 'A good thing')?
10. [Bruce Eckel](CppBruceEckel.md). Thinking in C++, second edition, volume 1. 2000. ISBN: 0-13-979809-9. Item 8: 'Constants', paragraph 'Summary': 'const-correctness can be a lifesaver for projects'.
11. [John Lakos](CppJohnLakos.md). Large-Scale C++ Software Design. 1996. ISBN: 0-201-63362-0. Chapter 9.1.6: 'Every object in a system should be const-correct'
2 changes: 1 addition & 1 deletion content/CppDoubleToStr.md
Expand Up @@ -117,7 +117,7 @@ External links


- [C++ FAQ lite page about double to std::string
conversion](http://www.parashift.com/c++-faq-lite/misc-technical-issues.html#faq-39.1)
conversion](https://isocpp.org/wiki/faq/misc-technical-issues#convert-num-to-string)



Expand Down
2 changes: 1 addition & 1 deletion content/CppGlobal.md
Expand Up @@ -19,7 +19,7 @@ visible in its [scope](CppScope.md)). A non-[const](CppConst.md)

* [1] [Andrei Alexandrescu](CppAndreiAlexandrescu.md). Modern C++ Design. 2001. ISBN: 0201704315. Item 10: 'Minimize global and shared data'.
* [2] Stephen C. Dewhurst. C++ Gotchas. 2003. ISBN: 0-321-12518-5. Gotcha #3: 'Avoid global variables'.
* [3] [C++ FAQ Lite](http://www.parashift.com/c++-faq/global-vars.html): 'The names of global variables should start with //' and 'Instead of using a global variable, you should seriously consider if there are ways to limit the variable's visibility and/or lifetime'.
* [3] [C++ FAQ Lite](https://isocpp.org/wiki/faq/coding-standards#global-vars): 'The names of global variables should start with //' and 'Instead of using a global variable, you should seriously consider if there are ways to limit the variable's visibility and/or lifetime'.
* [4] [Bjarne Stroustrup](CppBjarneStroustrup.md). The C++ Programming Language (3rd edition).ISBN: 0-201-88954-4. Chapter 1.8.2.a: 'Don't use global data (use members)'
* [5] [Jarrod Hollingworth](CppJarrodHollingworth.md) , Bob Swart, Mark Cashman, Paul Gustavson. Sams C++ Builder 6 Developer's Guide. ISBN: 0-672-32480-6. Chapter 3: 'Avoid using global variables'
* [6] [Jesse Liberty](CppJesseLiberty.md) . Sams teach yourself C++ in 24 hours. ISBN: 0-672-32224-2. Hour 5, paragraph 'Global variables': 'In C++, global variables are avoided because they can create very confusing code that is hard to maintain.'
Expand Down

0 comments on commit 031b18f

Please sign in to comment.