<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Most of the code is now compiled as C++ so probably not a big issue in practical terms. Also, we do run all code through
several msvc versions on AppVeyor so any non-msvs compliant code we may write should be discovered quickly. Code not passing the tests on AppVeyor should of course not be merged.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">As far as I understand the material from Microsoft, they support a large subset of C99 but some lesser used features aren’t
available. Getting a list of exactly what is and what isn’t supported is not easy to find though.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Just to be clear, I have no intention of updating the RFC as it is now. I don’t think the concerns raised here are incompatible
with the content of RFC3.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">/Kristian<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Fra:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Thomas Knudsen <knudsen.thomas@gmail.com>
<br>
<b>Sendt:</b> 16. januar 2019 16:12<br>
<b>Til:</b> Kristian Evers <kreve@sdfe.dk><br>
<b>Cc:</b> Even Rouault <even.rouault@spatialys.com>; proj@lists.osgeo.org<br>
<b>Emne:</b> Re: [PROJ] Motion: Adopt RFC3 - Dependency management<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">While improving, I think that the MSVC support of C99 is still incomplete, which could be a showstopper for going full C99<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Den ons. 16. jan. 2019 kl. 15.46 skrev Kristian Evers <<a href="mailto:kreve@sdfe.dk">kreve@sdfe.dk</a>>:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">Well, we *could* do that, but since we already have a few functions that return int<br>
instead of bool it would be more consistent to continue that pattern. I don't have<br>
strong opinion on the matter. I am curious to know though if there is any users<br>
of PROJ following the list that has a strict C89 requirement?<br>
<br>
/Kristian<br>
<br>
-----Oprindelig meddelelse-----<br>
Fra: Even Rouault <<a href="mailto:even.rouault@spatialys.com" target="_blank">even.rouault@spatialys.com</a>>
<br>
Sendt: 16. januar 2019 15:31<br>
Til: <a href="mailto:proj@lists.osgeo.org" target="_blank">proj@lists.osgeo.org</a><br>
Cc: Kristian Evers <<a href="mailto:kreve@sdfe.dk" target="_blank">kreve@sdfe.dk</a>><br>
Emne: Re: [PROJ] Motion: Adopt RFC3 - Dependency management<br>
<br>
Hi,<br>
<br>
there's a point that came to mind suddenly. About C99 adoption, that mean that <br>
we could use the 'bool' type in the C API for example. Do we want to do that ? <br>
The adverse consequence would be for third-party code using PROJ API and <br>
building with C89 only.<br>
<br>
Even<br>
<br>
> With +1 from Kristian, Even, Thomas and Howard I declare the motion passed.<br>
> <br>
> /Kristian<br>
> <br>
> Fra: Howard Butler <<a href="mailto:howard@hobu.co" target="_blank">howard@hobu.co</a>><br>
> Sendt: 14. januar 2019 16:08<br>
> Til: Thomas Knudsen <<a href="mailto:knudsen.thomas@gmail.com" target="_blank">knudsen.thomas@gmail.com</a>><br>
> Cc: Kristian Evers <<a href="mailto:kreve@sdfe.dk" target="_blank">kreve@sdfe.dk</a>>; PROJ <<a href="mailto:proj@lists.osgeo.org" target="_blank">proj@lists.osgeo.org</a>><br>
> Emne: Re: [PROJ] Motion: Adopt RFC3 - Dependency management<br>
> <br>
> +1 Howard<br>
> <br>
> <br>
> <br>
> On Jan 14, 2019, at 5:26 AM, Thomas Knudsen<br>
> <<a href="mailto:knudsen.thomas@gmail.com" target="_blank">knudsen.thomas@gmail.com</a><mailto:<a href="mailto:knudsen.thomas@gmail.com" target="_blank">knudsen.thomas@gmail.com</a>>> wrote:<br>
<br>
> +1 Thomas<br>
> <br>
> Den man. 14. jan. 2019 kl. 12.14 skrev Even Rouault<br>
> <<a href="mailto:even.rouault@spatialys.com" target="_blank">even.rouault@spatialys.com</a><mailto:<a href="mailto:even.rouault@spatialys.com" target="_blank">even.rouault@spatialys.com</a>>>:<br>
On lundi<br>
> 14 janvier 2019 10:20:11 CET Kristian Evers wrote:<br>
> <br>
> > PSC members,<br>
> ><br>
> ><br>
> ><br>
> > RFC3 about dependency management has been up for review for quite some<br>
> > time<br>
now. Since no comments has been reviewed since the last I update I<br>
> > regard this as ready for a vote by the PSC.<br>
> ><br>
> ><br>
> ><br>
> > The RFC is available here: <a href="https://github.com/OSGeo/proj.4/pull/1168" target="_blank">
https://github.com/OSGeo/proj.4/pull/1168</a><br>
> > <<a href="https://github.com/OSGeo/proj.4/pull/1168" target="_blank">https://github.com/OSGeo/proj.4/pull/1168</a>><br>
> ><br>
> ><br>
> ><br>
> > I’ll start with my +1.<br>
> <br>
> <br>
> +1 Even<br>
> <br>
> <br>
> ><br>
> ><br>
> > /Kristian<br>
> <br>
> <br>
> <br>
> --<br>
> Spatialys - Geospatial professional services<br>
> <a href="http://www.spatialys.com" target="_blank">http://www.spatialys.com</a><<a href="http://www.spatialys.com/" target="_blank">http://www.spatialys.com/</a>><br>
> _______________________________________________<br>
> PROJ mailing list<br>
> <a href="mailto:PROJ@lists.osgeo.org" target="_blank">PROJ@lists.osgeo.org</a><mailto:<a href="mailto:PROJ@lists.osgeo.org" target="_blank">PROJ@lists.osgeo.org</a>><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/proj" target="_blank">https://lists.osgeo.org/mailman/listinfo/proj</a><br>
> _______________________________________________<br>
> PROJ mailing list<br>
> <a href="mailto:PROJ@lists.osgeo.org" target="_blank">PROJ@lists.osgeo.org</a><mailto:<a href="mailto:PROJ@lists.osgeo.org" target="_blank">PROJ@lists.osgeo.org</a>><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/proj" target="_blank">https://lists.osgeo.org/mailman/listinfo/proj</a><br>
> <br>
<br>
<br>
-- <br>
Spatialys - Geospatial professional services<br>
<a href="http://www.spatialys.com" target="_blank">http://www.spatialys.com</a><br>
_______________________________________________<br>
PROJ mailing list<br>
<a href="mailto:PROJ@lists.osgeo.org" target="_blank">PROJ@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/proj" target="_blank">https://lists.osgeo.org/mailman/listinfo/proj</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>