[QUOTE=Digital Stimulus]
*: why one would include “Disable” in the variable name, when the value indicates exactly that is beyond me. This puts us in the position that “0”, which is usually taken to mean “false” or “off” actually means “on” in this case. Ah, how I do loves me some double negatives…
[/QUOTE]
That’s pretty common in hardware design. If a signal comes out of some device in a “high” condition when you might have preferred a “low”, rather than interposing an additional circuit to flip it, it is just labeled accordingly and the logic adjusts. To a computer, a double negative isn’t a problem.
[QUOTE=Musicat]
That’s pretty common in hardware design. If a signal comes out of some device in a “high” condition when you might have preferred a “low”, rather than interposing an additional circuit to flip it, it is just labeled accordingly and the logic adjusts. To a computer, a double negative isn’t a problem.
[/QUOTE]
Right, although: (1) this is software, with no cost ramifications and (2) the very word Disable not only confuses the issue, but is entirely unnecessary.
I realize this complaint shows more of my OCD/pedantic/neurotic side than I might like, but as someone who has agonized over…well, OK, spent maybe 10-15 minutes :)…over proper variable naming (is it too long? does it adequately express its use? am i following the standard? right polish or left polish notation?), it bugs me. It’s not always a good trait, but one of my pet peeves is poorly written code, even at this level of detail.
[QUOTE=Digital Stimulus]
Right, although: (1) this is software, with no cost ramifications and (2) the very word Disable not only confuses the issue, but is entirely unnecessary.
I realize this complaint shows more of my OCD/pedantic/neurotic side than I might like, but as someone who has agonized over…well, OK, spent maybe 10-15 minutes :)…over proper variable naming (is it too long? does it adequately express its use? am i following the standard? right polish or left polish notation?), it bugs me. It’s not always a good trait, but one of my pet peeves is poorly written code, even at this level of detail.
[/QUOTE]
I couldn’t agree with you more, but I don’t think the average software designer has near those deep ethics or agonizes for very long over what to call a parameter.
Too bad, because whatever was dashed off quickly without much thought may become imbedded and permanent for years.