true/false vs. yes/no
Mario Torre
neugens.limasoftware at gmail.com
Fri Oct 5 00:27:29 PDT 2012
Don't know about the variable value (does seem a bit inconsistent indeed,
although it makes some sense) but the yes/no is AFAIK pretty standard.
For example, this comes from the GNU.org guides (
http://www.gnu.org/prep/standards/html_node/Configuration.html):
"""
Configure the package to build and install an optional user-level
facility called feature. This allows users to choose which
optional features to include. Giving an optional parameter of
‘no’ should omit feature, if it is built by default.
"""
I guess the variable value makes some sense, since false is the value
assigned by answering "no" to the enable question.
Mario
Il giorno giovedì 4 ottobre 2012, David Holmes <david.holmes at oracle.com> ha
scritto:
> Just got bitten by the fact that the --enable-jfr flag takes the values
yes or no when passed to configure, but the ENABLE_JFR variable gets set to
true or false.
>
> Is there a reason for this inconsistency (is it normal for configure
based systems)?
>
> David
>
--
pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF
Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF
IcedRobot: www.icedrobot.org
Proud GNU Classpath developer: http://www.classpath.org/
Read About us at: http://planet.classpath.org
OpenJDK: http://openjdk.java.net/projects/caciocavallo/
Please, support open standards:
http://endsoftpatents.org/
More information about the build-infra-dev
mailing list