zhyang-dev/openfoam
1
0
Fork 0
mirror of https://develop.openfoam.com/Development/openfoam.git synced 2025-11-28 03:28:01 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
16,793 Commits 118 Branches 34 Tags
a1f209c48267d8b9ef7a76c562469db19c354e67
Commit Graph

19 Commits

Author SHA1 Message Date
Henry Weller
a1f209c482 doc/codingStyleGuide.org: Added specification references in class headers 2016-04-19 10:02:14 +01:00
Henry Weller
56fa7c0906 Update code to use the simpler C++11 template syntax removing spaces between closing ">"s 2016-01-10 22:41:16 +00:00
Henry Weller
c4d5f65a10 Completed update ...ErrorIn -> ...ErrorInFunction 
Avoids the clutter and maintenance effort associated with providing the
function signature string.
 2015-11-11 09:03:39 +00:00
Henry
99b99a46d4 codingStyleGuide: Minor updates 2015-02-25 10:55:51 +00:00
Henry
c2dd153a14 Copyright transfered to the OpenFOAM Foundation 2011-08-14 12:17:30 +01:00
andy
742fa75985 ENH: Updated web address 2011-06-14 12:53:43 +01:00
Henry
a3d18c648b codingStyleGuide: Added more details about Doxygen documentation 2011-02-09 12:37:33 +00:00
Henry
8ca3ebc569 Documentation: Updated style guide 2011-02-08 18:28:13 +00:00
Henry
51e2e6160d Documentation: Updated style guide 2011-02-08 18:25:44 +00:00
Henry
47c897577d Documentation: Updated style guide 2011-02-08 18:25:16 +00:00
Henry
c3cb632c24 Documentation: converted javadoc @ to LaTeX style \ in Doxygen code docs 2011-02-08 18:22:00 +00:00
Mark Olesen
35d3be771e STYLE: fix spelling, backslashes etc. in codingStyleGuide.org 
- now passes through LaTeX with fewer complaints.

- added note about braces for 'case' statements.

- could not formulate a sensible rule about when return statements
  need parentheses and when not.

- did not update codingStyleGuide.pdf ... I don't even know if it
  should be part of the git repo at all
 2010-06-01 10:19:11 +02:00
henry
49ccf0ffaa codingStyleGuide: updated and generated the pdf version. GUIDELINES removed. 2010-05-20 09:58:35 +01:00
Mark Olesen
5636df2b5a STYLE: use #+BEGIN_EXAMPLE / #+END_EXAMPLE in codingStyleGuide.org 
- seems to work more reliably than the previous indented colons
 2010-04-13 09:08:43 +02:00
Mark Olesen
b6f3bd4c23 STYLE: follow coding guide recommendation for '//- Destructor' 2010-04-12 11:55:52 +02:00
Mark Olesen
909e6b27e4 Apply coding style recommendations: 
- space between keyword and bracket in 'for(..)', 'if(..)', 'while(..)'
 2009-11-30 08:55:03 +01:00
Mark Olesen
6f14809234 Copy some of GUIDELINES -> codingStyleGuide.org 
- use ':' to prefix verbatim code instead of #+BEGIN_EXAMPLE / #+END_EXAMPLE
  for a somewhat better feeling for the indentation.
 2009-11-27 16:59:28 +01:00
Mark Olesen
fa93ce8cd7 coding style adherence 
- markup codingStyleGuide.org examples so they actually indent correctly

- use 'Info<<' as per codingStyleGuide instead of 'Info <<'
 2009-11-27 15:39:14 +01:00
Mark Olesen
d8cf3901d3 added doc/codingStyleGuide.org for central revision 2009-10-27 13:55:25 +01:00