Summary | sieve: empty allof generates 'false' instead of 'true' |
Queue | Ingo |
Queue Version | HEAD |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | ben (at) , jan (at) horde (dot) org |
Requester | gergely (at) risko (dot) hu |
Created | 08/28/2006 (6892 days ago) |
Due | |
Updated | 10/10/2006 (6849 days ago) |
Assigned | 09/25/2006 (6864 days ago) |
Resolved | 10/10/2006 (6849 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | Yes |
State ⇒ Resolved
changed the anyof test to return true without further rule criteria too.
specified.
to a test directory and test it if you do not believe, but I think it
is clear from the source also. Since it doesn't patch
Sieve_Test_Anyof class, but Sieve_Test_Allof only.
false" doesn't make any sense. "if true" doesn't make much sense
either, so I'm tending to disallow any rules that don't have
conditions specified.
running custom rule, if there is, please enlighten me. Anyway this was
the reason, why I bothered patching it.
gergely
specified. But this is an academical discussion anyway, because "if
false" doesn't make any sense. "if true" doesn't make much sense
either, so I'm tending to disallow any rules that don't have
conditions specified.
"anyof no criteria".
State ⇒ Feedback
"anyof no criteria".
Assigned to Jan Schneider
State ⇒ Assigned
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ sieve: empty allof generates 'false' instead of 'true'
Queue ⇒ Ingo
New Attachment: patch
State ⇒ Unconfirmed
but I specify not, then the generated code says 'if false' instead of
'is true'. Please keep in mind, that in mathematics (and because of
that in IT) "allof no conditions" evaluates to true, not to false.
That is anyof, which evaluates to false.