From bd026d26a7e15e0e58769309b60e02c46eb65b39 Mon Sep 17 00:00:00 2001 From: Masud Rahman Date: Thu, 24 Sep 2015 19:10:01 -0400 Subject: [PATCH] CppCoreGuidelines.md: fixes broken links. Some links had trailing quote marks, and the 'BDE' link was broken because the location had changed. --- CppCoreGuidelines.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index 81d5dac..33c2b92 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -10733,14 +10733,14 @@ Reference sections: ## RF.rules: Coding rules -* [Boost Library Requirements and Guidelines](http://www.boost.org/development/requirements.html"). +* [Boost Library Requirements and Guidelines](http://www.boost.org/development/requirements.html). ???. -* [Bloomberg: BDE C++ Coding](https://raw.githubusercontent.com/wiki/bloomberg/bde/bdestds.pdf"). +* [Bloomberg: BDE C++ Coding](https://github.com/bloomberg/bde/wiki/CodingStandards.pdf). Has a stong emphasis on code organization and layout. * Facebook: ??? * [GCC Coding Conventions](https://gcc.gnu.org/codingconventions.html). C++03 and (reasonably) a bit backwards looking. -* [Google C++ Style Guide](http://google-styleguide.googlecode.com/svn/trunk/cppguide.html"). +* [Google C++ Style Guide](http://google-styleguide.googlecode.com/svn/trunk/cppguide.html). Too timid and reflects its 1990s origins. [A critique from 2014](https://www.linkedin.com/pulse/20140503193653-3046051-why-google-style-guide-for-c-is-a-deal-breaker). Google are busy updating their code base and we don't know how accurately the posted guideline reflects their actual code.