Are there implication in handling all of them the same new way?
I mean if we assume that by something being equal to 0 we disable it
, would it cause an undesirable semantic change in some cases?
What about the cases when there is no sense in something being
disabled how we will treat the 0 value then?
For bools it is even more scary. If you say that bool = 0 sets the
default this is a bug because IMO bool = 0 means bool = false and
this is an explicit setting.
Now it is broken but it is consistent. I am concerned that we are
heading into the case when the options will be broken on case by
case basis.
-------- Original Message --------
#2257: Setting int option to 0 yields the default value
---------------------------------+---------------------------------
Reporter: jhrozek | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone: NEEDS_TRIAGE
Component: SSSD | Version: 1.11.4
Resolution: | Keywords:
Blocked By: | Blocking:
Tests Updated: 0 | Coverity Bug:
Patch Submitted: 0 | Red Hat Bugzilla:
Design link: | Design review: 0
Fedora test page: | Chosen:
Candidate to push out: 0 |
---------------------------------+---------------------------------
Feature Milestone:
Release Notes:
---------------------------------+---------------------------------
Comment (by jhrozek):
I found out this is not specific to the single option, but all int and
bool options are affected.
--
Ticket URL: <https://fedorahosted.org/sssd/ticket/2257#comment:1>
SSSD <http://fedorahosted.org/sssd>
System Security Services Daemon