STYLE: consistent ordering of "inline explicit" vs. "explicit inline"

- resolve in favour of "inline explicit", which had marginally more
  uses and provides consistent prefixing for inline methods.
This commit is contained in:
Mark Olesen
2018-05-30 12:11:13 +02:00
parent f9fe71815a
commit 2aaae74ee1
23 changed files with 53 additions and 53 deletions

View File

@ -86,7 +86,7 @@
// - 0: different
// - +1: identical
// - -1: same face, but different orientation
static inline int compare(const triFace&, const triFace&);
static int compare(const triFace&, const triFace&);
#+end_src
or
#+begin_src C++
@ -95,7 +95,7 @@
// - 0: different
// - +1: identical
// - -1: same face, but different orientation
static inline int compare(const triFace&, const triFace&);
static int compare(const triFace&, const triFace&);
#+end_src
*not*
#+begin_src C++
@ -103,7 +103,7 @@
// - 0: different
// - +1: identical
// - -1: same face, but different orientation
static inline int compare(const triFace&, const triFace&);
static int compare(const triFace&, const triFace&);
#+end_src
+ List can be nested for example
#+begin_src C++