The following issue has been SUBMITTED.
======================================================================
http://public.kitware.com/Bug/view.php?id=13092
======================================================================
Reported By: Christoph Anton Mitterer
Assigned To:
======================================================================
Project: CMake
Issue ID: 13092
Category: CMake
Reproducibility: always
Severity: feature
Priority: normal
Status: new
======================================================================
Date Submitted: 2012-04-01 20:13 EDT
Last Modified: 2012-04-01 20:13 EDT
======================================================================
Summary: change set() behaviour when value is inset, to
define the variable as true
Description:
Hi.
To me it seems a bit inconsistent that:
set(FOO)
unsets FOO.
Given that you interpret a unset variable as false and given that unset() is the
opposite of set(), it would IMHO make more sense to set FOO to true.
This would also be more consistent with C/C++ preprocessor's understanding of
true/false.
And after all, that a command called "set" unsets is a bit awkward.
Of course this will break things, but given your nice policy mechanism this
shouldn't really harm.
Cheers,
Chris.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2012-04-01 20:13 Christoph Anton MittererNew Issue
======================================================================
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
