Skip to content

Latest commit

 

History

History
41 lines (29 loc) · 2.57 KB

File metadata and controls

41 lines (29 loc) · 2.57 KB

Secure Systems Lab C/C++ Style Guide

These guidelines provide examples of what to do (or not to do) when writing C/C++ code for the projects of the Secure Systems Lab in the NYU Tandon School of Engineering.

The style guide provided here is intended to improve the readability of code and make it consistent across the wide spectrum of C/C++ code. The features that your code must have are readability, security, correctness, robustness and performance.

In general for C/C++ programming languages we use Google C++ Style Guide.

Since security is an important for Secure Systems Lab, we also should follow some security rules.

  • For secure C++ coding please have a look follow link: The C++ rules.

  • For secure C coding please have a look follow link: The C rules.

See Also

Five particularly important books related to C++ are:

  1. Effective C++: 55 Specific Ways to Improve Your Programs and Designs by Scott Meyers.
  2. Effective Modern C++: 42 Specific Ways to Improve Your Use of C++11 and C++14 by Scott Meyers.
  3. Also interesting and useful are More Effective C++ and Effective STL by Scott Meyers.
  4. Large-Scale C++ Software Design by John Lakos.
  5. The C++ Programming Language, 4th Edition by Bjarne Stroustrup.

Two books related to C are:

  1. The C Programming Language by Brian W. Kernighan and Dennis M. Ritchie.
  2. Expert C Programming: Deep C Secrets by Peter van der Linden.

If you have not read them yet, we highly recommend you to read, you might learn something.