Replace endless if (** iswm ..) blocks with hash map about dlfilter HOT 12 CLOSED

Might be.

from dlfilter.

AFAIK, hash tables enable you to look up the value against a key quickly for large numbers of keys. I believe that you can iterate over the hash table too, though that is not their purpose.

I am unsure how we can use a hash table for fast lookup of iswm matching - we can use it as an array and iterate the values in order to get the values to iswm with, but that is unlikely to be any faster then the long list of if iswm.

But if there is a way to use a hash table effectively let me know and I will code it.

from dlfilter.

Hmmm - it seems that $hfind(hashtable, message, 1, W) uses the hash table item or data as wildcard text - so perhaps this is possible.

from dlfilter.

Good find, I didn't know about that $hfind() option. My initial idea was just looping over hashmap/items, to make filters more easier to maintain, compared to endless if statements.

The hashmap should also contain the appropriate method to call on match, e.g.:
filter <--> method
*SpR JUKEBOX*filesize* TextSetNickColor
*DCC GET COMPLETE*from*slot*open* DLF_textfilter

from dlfilter.

Yes - we will need different hash tables for each group.

I have this mostly done on my PC (but not yet on GitHub) - when I do the next commit it would be helpful if you could deskcheck old and new code to make sure that I have create a like for like solution.

from dlfilter.

$hfind will be at least one order of magnitude more efficient/faster (and possibly two orders of magnitude) than a loop or list of if statements.

from dlfilter.

It really depends.

Hash map should be O(1), if Khaled has implemented it properly. However, since that $hfind() is a wildcard match on key, it probably loops internally and is O(n).

from dlfilter.

Yes - but it will be machine code (C?) rather than interpreted mIRC script.

from dlfilter.

I presume that mIRC compiles the script internally to bytecode/assembly-like on load and uses that. But you are probably right.

We can always do a performance test if we really care...

from dlfilter.

I don't really care TBH. It was performing OK on my PC as a list of IF statements.

But I think using hashtables is both more elegant and more maintainable.

from dlfilter.

Exactly. The if's just tickle my inner perfectionist in the wrong way.

from dlfilter.

Coded - see #7

from dlfilter.