<div dir="ltr">Thanks all for your suggestions.<div>I did some more research and it seems to be an issue with the preprocessor on Windows.</div><div><br></div><div>Adding some brackets solves the issue as well:</div><div>// old</div><div>constexpr int64_t GDAL_PAM_DEFAULT_NODATA_VALUE_INT64 = std::numeric_limits<int64_t>::min();</div><div>constexpr uint64_tGDAL_PAM_DEFAULT_NODATA_VALUE_UINT64= std::numeric_limits<uint64_t>::max();</div><div>// new:</div><div>constexpr int64_t GDAL_PAM_DEFAULT_NODATA_VALUE_INT64 =<b><font color="#ff0000">(</font></b>std::numeric_limits<int64_t>::min<b><font color="#ff0000">)</font></b>();</div><div>constexpr uint64_t GDAL_PAM_DEFAULT_NODATA_VALUE_UINT64 =<b><font color="#ff0000">(</font></b>std::numeric_limits<uint64_t>::max<b><font color="#ff0000">)</font></b>();</div><div><br></div><div>I'm not sure what the impact would be for non-windows compilers, but if no impact could this be changed in the code?<br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><br></div><div dir="ltr">Thanks,<br>
<br>Paul Meems<br>
</div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Op za 17 dec. 2022 om 07:10 schreef <<a href="mailto:dg0yt@darc.de">dg0yt@darc.de</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I'm not using MSVC, so this is a guess:<br>
Are you including 'windows.h' without 'NOMINMAX' being defined?<br>
Then you will get macros which interfere with the limits code.<br>
<br>
Regards, Kai.<br>
<br>
> Paul Meems <<a href="mailto:bontepaarden@gmail.com" target="_blank">bontepaarden@gmail.com</a>> hat am 17.12.2022 00:46 CET geschrieben:<br>
> <br>
> <br>
> Thanks, Kurt for your response.<br>
> <br>
> I'm getting a very vague error message:<br>
> E0040 expected an identifier.<br>
> <br>
> <br>
> Regards,<br>
> <br>
> Paul<br>
> <br>
> <br>
> Op za 17 dec. 2022 om 00:40 schreef Kurt Schwehr <<a href="mailto:schwehr@gmail.com" target="_blank">schwehr@gmail.com</a>>:<br>
> > What exact error are you getting?<br>
> > <br>
> > <br>
> > On Fri, Dec 16, 2022 at 3:31 PM Paul Meems <<a href="mailto:bontepaarden@gmail.com" target="_blank">bontepaarden@gmail.com</a>> wrote:<br>
> > > Hello List,<br>
> > > <br>
> > > We're trying to update MapWinGIS which is using the GDAL libraries from <a href="http://gisinternals.com" rel="noreferrer" target="_blank">gisinternals.com</a> (<a href="http://gisinternals.com" rel="noreferrer" target="_blank">http://gisinternals.com</a>)<br>
> > > Currently, we use the stable daily of December 9: release-1928-gdal-3-5-mapserver-8-0<br>
> > > <br>
> > > I'm using VS2019 (on Windows) to compile and I'm having issues with two lines in gdal_pam.h, around line 215.<br>
> > > We need to change these two lines:<br>
> > > <br>
> > > * constexpr int64_t GDAL_PAM_DEFAULT_NODATA_VALUE_INT64 = std::numeric_limits<int64_t>::min();<br>
> > > * constexpr uint64_t GDAL_PAM_DEFAULT_NODATA_VALUE_UINT64 = std::numeric_limits<uint64_t>::max();<br>
> > > To<br>
> > > * constexpr int64_t GDAL_PAM_DEFAULT_NODATA_VALUE_INT64 = LLONG_MIN;<br>
> > > * constexpr uint64_t GDAL_PAM_DEFAULT_NODATA_VALUE_UINT64 = LLONG_MAX;<br>
> > > I prefer not to alter the files from <a href="http://gisinternals.com" rel="noreferrer" target="_blank">gisinternals.com</a> (<a href="http://gisinternals.com" rel="noreferrer" target="_blank">http://gisinternals.com</a>). Is this what we can solve on our end?<br>
> > > Is it related to the C++ version? We use these:<br>
> > > <br>
> > > * ISO C++14 Standard (/std:c++14)<br>
> > > * ISO C11 Standard (/std:c11)<br>
> > > Thanks for any advice.<br>
> > > <br>
> > > Paul Meems<br>
> > > <br>
> > > _______________________________________________<br>
> > > gdal-dev mailing list<br>
> > > <a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a><br>
> > > <a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
> > > <br>
> _______________________________________________<br>
> gdal-dev mailing list<br>
> <a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
</blockquote></div>