--- Comment #2 from Jan Schoonderbeek <> 2010-10-06 
20:59:57 UTC ---
While I understand your original motivation and your call for simplicity, I
disagree with the implications. Mentioning this use on the IRC channel gave me
3 out of 3 people (including active developers) who didn't know that < actually
means ≤. Not a really statistically representative poll, but nevertheless...

If you strive for simplicity, then have < really mean "less than". As it stands
queries are harder to read because anything seemingly noted as "less than X"
actually includes X, or, in my case, "less than X" is actually the correct
notation for "less than Y" (or alternatively "less than X""also, not X").

However, if there are no strong objections to using characters ≤ and ≥, then I
believe we can agree that query reading is strongly improved while not making
it hard to accomplish the common case (which you suggest can still be
accomplished using < and > if applications really don't care about the

When following your reasoning I do see that the default setting should remain
"old behaviour", which makes a case for something like "$smwStrictComparator =
true" to switch on the extra comparators AND switch "equal or less" to ≤.

To summarize:
Notwithstanding the forementioned, I still believe the current implementation
where writing [[Maturity::<9]] is actually not "less than nine" is confusing
and needs to be remedied. Please add comparators that are truly "less than" and
"greater than", off by default, with an option to switch them on in
LocalSettings.php using a suitable boolean variable.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to