From a06b75ba9e9fad7f3a9315f9c4156b8c7647481f Mon Sep 17 00:00:00 2001
From: "Joachim Wuttke (h)" <j.wuttke@fz-juelich.de>
Date: Wed, 11 Nov 2015 22:29:21 +0100
Subject: [PATCH] rm obsolete STYLE

---
 pub/lib/STYLE | 35 -----------------------------------
 1 file changed, 35 deletions(-)
 delete mode 100644 pub/lib/STYLE

diff --git a/pub/lib/STYLE b/pub/lib/STYLE
deleted file mode 100644
index c9a6ef65..00000000
--- a/pub/lib/STYLE
+++ /dev/null
@@ -1,35 +0,0 @@
-== checks ==
-
-mylint.py --counting=detailed `lssrc` > ~/h
-
-== include's ==
-
-- Block 1: Standard software
-  - C standard library: cstdlib cstdio cstring cmath *.h sys/*.h
-  - C++ standard library: iostream fstream string vector map algorithm
-  - boost
-  - GSL
-- Block 2: Our own libs
-  - trivia readplus yamlfreeze lmfit kww
-- Block 3: Current project
-
-== function arguments and "const" qualifier ==
-
-- never use "const" with simple data types
-
-    double f( double x ); // and not ( const double x )
-
-- prefer passing complex data types (including string) by reference:
-
-    double sum( const vector<int>& row );
-
-- generally, when passing arguments by & reference: not putting "const"
-  means that mutation of the argument is intended
-
-- omitting "const" has the side effect, that the function cannot be
-  called with a constructor in place of the argument:
-
-     out = sum( vector<int>(7) ); // only allowed when arg is declared const
-
-- "const" with pointer arguments is poorly understood (even less so with
-  shared_ptr)
-- 
GitLab