Changes between Version 5 and Version 6 of CodingPatterns


Ignore:
Timestamp:
May 15, 2019, 12:29:08 PM (5 years ago)
Author:
mdavis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CodingPatterns

    v5 v6  
    33This page documents coding patterns followed in the GEOS codebase. 
    44
    5 The patterns are intended to improve the following:
     5The patterns are intended to improve: understandability, consistency, performance, and memory safety.
    66
    7  * Understandability
    8  * Performance
    9  * Memory safety
    10 
    11 Older GEOS code may not adhere to all patterns, but the goal is to update it when possible.  New code should follow the patterns given here, unless this is not possible for compatibility reasons.
     7**Code should follow the patterns given here, unless this is not possible for compatibility reasons. Older GEOS code may not adhere to all patterns, but the goal is to update it when possible.** 
    128
    139= Patterns
    … …  
    1511== Object References
    1612
    17 * Created objects should be returned as a `std::unique_ptr<Object>`
    18 * Taking ownership of a returned object should be done as a `std::unique_ptr<Object>`
     13* Return created objects using `std::unique_ptr<Object>`
     14* To take ownership of a returned object use `std::unique_ptr<Object>`
    1915
    2016= To Be Investigated