<html><head></head><body>Thanks for the link.<br>
The backwards compatibility is something worth mentioning in the release notes, so that people can use it right away.<br>
<br><br><div class="gmail_quote">Am 1. Juli 2018 00:12:19 MESZ schrieb Craig Scott <craig.scott@crascit.com>:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr">(Subject changed to be specific to this discussion)<br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jun 30, 2018 at 3:13 PM, Hendrik Sattler <span dir="ltr"><<a href="mailto:post@hendrik-sattler.de" target="_blank">post@hendrik-sattler.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It would actually make even more sense to rename cmake_minimum_required() to cmake_version_required() with the new syntax or something similar. Users of the old function cannot use the new syntax in older cmake versions and the old name does not actually fit the new functionality.<br></blockquote><div><br></div><div>Actually older versions can use the new syntax and this is indeed the specific reason why the new syntax is the way it is. Older CMake versions will see the extra dots as being version component separators and will end up effectively ignoring the max part. The nett result is that older versions will continue to treat the min version as the policy setting just like they have been to date. Newer versions of CMake will be able to take advantage of the extra information provided by the max part to allow newer policies to be enforced.</div><div><br></div><div>Regarding the renaming, a very similar discussion took place in the merge request itself, so I'll refer you to there for details:</div><div><br></div><div><a href="https://gitlab.kitware.com/cmake/cmake/merge_requests/1864#note_389157">https://gitlab.kitware.com/cmake/cmake/merge_requests/1864#note_389157</a><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Am 30. Juni 2018 00:05:25 MESZ schrieb "Alan W. Irwin" <<a href="mailto:irwin@beluga.phys.uvic.ca">irwin@beluga.phys.uvic.ca</a>>:<br>
>On 2018-06-29 14:46-0400 Robert Maynard wrote:<br>
>[...]<br>
>> * The "cmake_minimum_required()" and "cmake_policy(VERSION)"<br>
>> commands now accept a version range using the form<br>
>> "<min>[...<max>]". The "<min>" version is required but policies are<br>
>> set based on the "<max>" version. This allows projects to specify a<br>
>> range of versions for which they have been updated and avoid<br>
>> explicit policy settings.<br>
>[...]<br>
><br>
>I suggest the following change to the above description:<br>
><br>
>but policies are set based on the "<max>" version.<br>
><br>
>==><br>
><br>
>but policies are set based on the minimum of the running CMake and<br>
>"<max>" versions.<br>
><br>
>I prefer the latter because it immediately answers the question implied<br>
>by the former, i.e.,<br>
>what happens if the running version is less than max?<br>
</blockquote></div><br>Seems reasonable. I've created a MR with a slight tweak to your wording for this <a href="https://gitlab.kitware.com/cmake/cmake/merge_requests/2180">here</a>.<br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Craig Scott<br><div>Melbourne, Australia</div><div><a href="https://crascit.com" target="_blank">https://crascit.com</a><br></div></div></div></div></div></div></div>
</div></div>
</blockquote></div></body></html>