[vtk-developers] [ANNOUNCE] New module system landing

[David Thompson]

REQUIRE/ATTEMPT/AVOID/FORBID make the most sense to me.  I could also come up with quite a few alternate words for each option if you like... :-)

  YES = REQUIRE = FORCE = ENABLE = NEED = COMPEL = INCLUDE
  WANT = ATTEMPT = TRY = PREFER = YEARN_FOR
  DONT_WANT = AVOID = CANCEL = UNWANTED = SHUN
  NO = FORBID = DISABLE = REJECT = DISQUALIFY = PREVENT = EXCLUDE

It would be nice, as David Gobbi suggested, to warn when option-valued cache variables are set to a string that is not an accepted option.

	2 cents,
	David

> On Feb 1, 2019, at 15:08, Ben Boeckel via vtk-developers <vtk-developers at vtk.org> wrote:
> 
> On Fri, Feb 01, 2019 at 12:26:18 -0700, David Gobbi wrote:
>> On Fri, Feb 1, 2019 at 11:58 AM Ben Boeckel <ben.boeckel at kitware.com> wrote:
>>> It was partially done to get
>>> away from the default verbiage of `option` which uses `ON/OFF` since it
>>> isn't really a CMake boolean.
>> 
>> That's like saying that if we use "0" and "1" as binary digits, we have
>> to make up new names/symbols for 0 and 1 when using decimal...
> 
> Should they instead be called `MUST_BUILD` and `CANNOT_BUILD` to avoid
> all ambiguity? One other difference is actually that the old `ON/OFF` is
> actually `YES/DONT_WANT` in the new module system since telling the old
> system `OFF` didn't prevent the building of the module whereas `NO`
> errors out if it would otherwise be built. So it's might be closer to
> "0" and "1" in binary meaning "0" and "3" in the decimal…
> 
> --Ben
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Search the list archives at: http://markmail.org/search/?q=vtk-developers
> 
> Follow this link to subscribe/unsubscribe:
> https://vtk.org/mailman/listinfo/vtk-developers
>