Rename OR_GREATER to OR_LATER

[terrajobst]

Based on feedback

[sebastienros]

Can we just count the legal votes?

[dotMorten]

OR_GREATER makes more sense IMHO. It's a version check, not a date check. 5.1 could potentially be released after 6.0.

It also makes sense as part of the discussion we had about potentially having range check support in the future. Ie #if NETVERSION>=5.0.

[davkean]

Windows does OR_GREATER: https://docs.microsoft.com/en-us/windows/win32/sysinfo/getting-the-system-version.

[ericsampson]

Will a N-1 minor release ever happen after a N major? If so, @dotMorten has a point...

[dotMorten]

@ericsampson My understanding is it isn't the plan, but also never say never...

Can't we all also agree that the latest .NET version is just sooooo much greater than the previous one? :-D

[JamesNK]

Docs tend to use "or later" when talking about version numbers:

https://www.google.com/search?q=site%3Adocs.microsoft.com+%22or+later%22

[Tyrrrz]

How long until full pattern matching support in compilation directives?

[Nirmal4G]

@dotMorten If you guys are sure about range check then do that instead of this.

I think having two similar things might make it worse than intented.

I vote for range check. It's simple.

[dotMorten]

@Nirmal4G range check is a potential future long-term feature. Nothing for sure.

[mehrandvd]

OR_GREATER makes more sense IMHO. It's a version check, not a date check. 5.1 could potentially be released after 6.0.

It also makes sense as part of the discussion we had about potentially having range check support in the future. Ie #if NETVERSION>=5.0.

What about OR_NEWER?

[devlead]

Greater makes more sense IMHO, there might be things released later that aren't greater.

[umbarov]

GREATER goes well with numbers. LATER goes well with code names.

NET5_0_OR_GREATER

NET_PUMPKIN_OR_LATER

[PathogenDavid]

If we’re going to have a bikeshed party, I’d like to complicate things by proposing _OR_NEWER, which is what Unity uses.

(I’m half joking, but I do think there’s some merit to remaining consistent with a segment of the .NET ecosystem that has actively encouraged/enabled platform-specific code through preprocessor for quite some time.)

[theo-albers]

I suggest OR_HIGHER. This works for none versions as well, like "bachelor's degree or higher".

[jaredpar]

Do we need to take this now OR_LATER?

[dotMorten]

@jaredpar I think it needs to be AND_NEVER

[terrajobst]

OK, considering the voting distribution I think we leave this as OR_GREATER.