[geos-commits] [SCM] GEOS branch main updated. 0568dc93ad05b71249f34eca683e6e958f2ee5e7

[git at osgeo.org]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GEOS".

The branch, main has been updated
       via  0568dc93ad05b71249f34eca683e6e958f2ee5e7 (commit)
      from  975fa0008472416c4690b2ff1e7d843342c5fb92 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 0568dc93ad05b71249f34eca683e6e958f2ee5e7
Author: Martin Davis <mtnclimb at gmail.com>
Date:   Thu May 23 20:28:43 2024 -0700

    Update DEVELOPER-NOTES.md

diff --git a/DEVELOPER-NOTES.md b/DEVELOPER-NOTES.md
index 77a021416..8b47e4b1a 100644
--- a/DEVELOPER-NOTES.md
+++ b/DEVELOPER-NOTES.md
@@ -23,7 +23,15 @@
 
     * Yes, we know in your last job you were taught all member variables are prefixed with `m_`, but please don't.
 
+## C/C++ Guidelines
 
+C++ (in particular) is a large complex language, with many patterns that have evolved over the years.
+The GEOS codebase has also evolved over the years, but parts still exhibit obsolete language
+or project patterns.
+When porting or adding code, follow the style of the most recently written code (use the commit history to find this).
+
+In general, we follow the [C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines).
+The following summarizes some of the key patterns used in GEOS.
 
 ### Manage Lifecycles
 

-----------------------------------------------------------------------

Summary of changes:
 DEVELOPER-NOTES.md | 8 ++++++++
 1 file changed, 8 insertions(+)


hooks/post-receive
-- 
GEOS