Changes between Version 34 and Version 35 of MapGuideCodingStandards


Ignore:
Timestamp:
Sep 18, 2022, 10:32:16 PM (20 months ago)
Author:
jng
Comment:

A note about expected C++ standards version

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideCodingStandards

    v34 v35  
    66
    77||'''Revision'''||'''Date'''||'''Author'''||'''Comment'''||
     8||1.6.4||19 Sep, 2022||Jackie Ng||Clarified expected C++ standards level||
    89||1.6.3||26 Jan, 2015||Jackie Ng||Added section about argument checking||
    910||1.6.2||9 Dec, 2012||Jackie Ng||More about C++ documentation||
     
    1920 * The maintenance is done by many different individuals over the lifetime of a given software product and not the original developer.
    2021 * Guidelines improve readability of the software and help make the learning curve of new developers easier.
     22
     23== C++ Standards Version ==
     24
     25MapGuide (and FDO) are expected to be built on a compiler that supports **C++11**
     26
     27Avoid using language constructs or standard library features that are introduced in C++ versions newer than this version
     28
     29Avoid using language constructs or standard library features that were introduced in C++ versions prior to this version, but have since been deprecated (eg. Usage of `std::auto_ptr` instead of `std::unique_ptr`)
    2130
    2231== Consistency with .NET ==