Describe the bug
As new VC versions come out, max doesn't recognize them correctly. There should be a way to say "It is at least version X" (where X is the last-known version) and continue to compile assuming support for things that were supported in version X.
Instead, the last-known version uses == as a test and fails. The next older version uses >= and passes. So it assumes it is X-1.
To Reproduce
Steps to reproduce the behavior:
Grab a version of max that doesn't support the latest VC version.
Compile.
Expected behavior
max should work and build as expected with the latest known version.
Maybe it should generate a compile-time warning.
Observed behavior
max says it is the second-to-latest known version.
Platform (please complete the following information if applicable):
OS: Windows 10
Compiler & version: MSVC 15.9
max commit SHA: 849feb52d8ac4ddc8c2f4147d4b01be0013ca7da
Describe the bug As new VC versions come out, max doesn't recognize them correctly. There should be a way to say "It is at least version X" (where X is the last-known version) and continue to compile assuming support for things that were supported in version X.
Instead, the last-known version uses == as a test and fails. The next older version uses >= and passes. So it assumes it is X-1.
To Reproduce Steps to reproduce the behavior:
Expected behavior max should work and build as expected with the latest known version. Maybe it should generate a compile-time warning.
Observed behavior max says it is the second-to-latest known version.
Platform (please complete the following information if applicable):
Additional context