PROJ/src/pj_zpoly1.c, branch azp Forked from https://github.com/OSGeo/PROJ cpp conversion: minimal steps to fix compilation errors, not warnings 2018-12-26T09:08:53+00:00 Even Rouault even.rouault@spatialys.com 2018-12-18T19:24:11+00:00 610957f7035242f15743c399ffd429b92bc36206 






Remove angle brackets for proj headers (#849)
2018-03-11T12:17:07+00:00

Thomas Knudsen
busstoptaktik@users.noreply.github.com

2018-03-11T12:17:07+00:00

ab87b8ef0af7ef888b7d810db610ead6eb784d71

* Avoid using angle brackets for PROJ headers.

Switching from #include <proj.h> to #include "proj.h",
and correspondingly for projects.h and proj_api.h,
reduces the risk of accidentally picking up a system
installed older version of the header while building
a new version of PROJ.

* Also handle geodesic.h





* Avoid using angle brackets for PROJ headers.

Switching from #include <proj.h> to #include "proj.h",
and correspondingly for projects.h and proj_api.h,
reduces the risk of accidentally picking up a system
installed older version of the header while building
a new version of PROJ.

* Also handle geodesic.h







Declare non-local variables as const where possible
2017-12-17T22:34:40+00:00

Aaron Puchert
aaron.puchert@sap.com

2017-11-17T16:46:34+00:00

a07501a165e6f2521c9aa13fa63fab33cf67d876

Having non-const variables of static lifetime or even global scope is
usually a bad idea. These variables are inherently constants, and this
should be enforced.

This required marking some functions as not modifying input parameters
and marking some pointers as pointers to const.

One advantage is that the compiler usually puts const static variables
in a read-only code segment, so they can't be modified physically.
This can be verified with `nm` (on POSIX systems).

To avoid changes to the public API, functions returning non-const
pointers to data tables were left intact, but the returned data may not
be modified. Internally we prefer using the proj_list_* functions over
the pj_get_*_ref functions, because the former return const pointers.





Having non-const variables of static lifetime or even global scope is
usually a bad idea. These variables are inherently constants, and this
should be enforced.

This required marking some functions as not modifying input parameters
and marking some pointers as pointers to const.

One advantage is that the compiler usually puts const static variables
in a read-only code segment, so they can't be modified physically.
This can be verified with `nm` (on POSIX systems).

To avoid changes to the public API, functions returning non-const
pointers to data tables were left intact, but the returned data may not
be modified. Internally we prefer using the proj_list_* functions over
the pj_get_*_ref functions, because the former return const pointers.







Fix compiler warnings with gcc 4.4
2015-10-27T09:47:28+00:00

Even Rouault
even.rouault@spatialys.com

2015-10-27T09:47:28+00:00

d227fcf36d550f244eccc5fedc2e08908451c27b












remove SCCSID and lint stuff from all source files
2009-01-26T17:39:35+00:00

Frank Warmerdam
warmerdam@pobox.com

2009-01-26T17:39:35+00:00

04058618706b306520f1a4656a521ba555601b3b

git-svn-id: http://svn.osgeo.org/metacrs/proj/trunk@1515 4e78687f-474d-0410-85f9-8d5e500ac6b2





git-svn-id: http://svn.osgeo.org/metacrs/proj/trunk@1515 4e78687f-474d-0410-85f9-8d5e500ac6b2







New
1999-03-18T16:34:52+00:00

Frank Warmerdam
warmerdam@pobox.com

1999-03-18T16:34:52+00:00

565a4bd035b9d4a83955808efef20f1d8dfa24cf

git-svn-id: http://svn.osgeo.org/metacrs/proj/trunk@776 4e78687f-474d-0410-85f9-8d5e500ac6b2





git-svn-id: http://svn.osgeo.org/metacrs/proj/trunk@776 4e78687f-474d-0410-85f9-8d5e500ac6b2