Apply 4-spaces standard indenting,

120 column wrapping, and some basic
consistency around parens, operators and
function signatures. Code now matches
editorconfig so patches should largely
lack whitespace noise, and folks trying
to "match the code around" should find
it easier to figure out what "match"
means.
Per https://lists.osgeo.org/pipermail/geos-devel/2018-September/008539.html

.astylerc

@@ -0,0 +1,12 @@
+--style=stroustrup
+--indent=spaces=4
+--max-code-length=120
+--lineend=linux
+--unpad-paren
+--pad-oper
+--align-pointer=type
+--align-reference=type
+--break-closing-braces
+--add-braces
+--break-return-type
+--break-after-logical

CMakeLists.txt

@@ -13,12 +13,12 @@
 cmake_minimum_required(VERSION 3.1.3)
 
 if(NOT CMAKE_VERSION)
-    set(CMAKE_VERSION
-      "${CMAKE_MAJOR_VERSION}.${CMAKE_MINOR_VERSION}.${CMAKE_PATCH_VERSION}")
+  set(CMAKE_VERSION
+    "${CMAKE_MAJOR_VERSION}.${CMAKE_MINOR_VERSION}.${CMAKE_PATCH_VERSION}")
 endif()
 
 if(POLICY CMP0048)
-    cmake_policy(SET CMP0048 NEW)
+  cmake_policy(SET CMP0048 NEW)
 endif()
 #################################################################################
 # Set GEOS project