Displaying 2 results from an estimated 2 matches for "insert_idx".
2019 Oct 04
1
imapsieve administrator scripts are not executed in the order they are defined
...box_rules_match(...): The comment in this function states
"Insert sorted by rule index", but in case the index of the rule to be
inserted is higher than any index already in the "rules" array, the rule is
inserted in position 0 instead of being appended to the end, because
"insert_idx" is initialized with 0.
Since the rule for "*.Spam" is a pattern rule, it is the first rule to be
inserted into "rules" (in imap_sieve_mailbox_rules_match_patterns(...)).
Afterwards the rule for "Inbox" is always inserted at position 0 (in
imap_sieve_mailbox_rule...
2007 Mar 15
5
[PATCH 0/5] fix gcc warnings in CVS HEAD
Hi,
I have rewritten the patches I submitted earlier today for the CVS
HEAD. Some of the changes were already committed months ago.
On 2007/03/15 12:30, Timo Sirainen <tss at iki.fi> wrote:
> That's ok, but I'm not sure about bsearch_insert_pos(). It's the way it
> is mostly because I wanted to keep bsearch() API. If it can't return
> void * then maybe it could be