Difference between revisions of "C/C++"

From HCL
Jump to: navigation, search
Line 16: Line 16:
 
== General ==
 
== General ==
 
* Don't use non-standard functions, like [http://en.wikipedia.org/wiki/Itoa itoa]
 
* Don't use non-standard functions, like [http://en.wikipedia.org/wiki/Itoa itoa]
 +
* [http://www.gnu.org/software/libc/manual/html_node/Program-Arguments.html Handling program arguments]
 
* [http://en.wikipedia.org/wiki/Dynamic_loading Dynamic loading of shared libraries]
 
* [http://en.wikipedia.org/wiki/Dynamic_loading Dynamic loading of shared libraries]
  

Revision as of 12:35, 12 February 2010

Coding

Commenting

  • Place Doxygen comments in header files (before declarations of namespaces/classes/structs/typedefs/macros) and main source files (for documenting tools and tests)
  • Use double forward slash for short comments in the code

C++

  • Mixing C/C++
  • Template C++ is preferrable from the point of view of runtime performance
  • Use plain C unless you need flexible data structures or STL/Boost functionality
  • Provide main API in C

General

Creating libraries with Autotools

  • Prepare two sets of headers:
    • includes (for the include directory): include_HEADERS = ...
    • sources (internal C data structures and C++ template classes): library_SOURCES = library.h ...
      • library.h is a precompiled header (contains common headers and symbols), which is to be included in most of source files of the library