Yeah even EquipCompare which was the addon EQCompare was originally written to replace has gotten updated and become much much better than EQCompare because it actually gets updated. EQCompare is dead, if you want the lightwight replacement without configuration that uses the blizzard compare tooltips get tekKompare, if you want the heavier replacement with more options that replaces the blizzard tooltips (like EQCompare does) get EquipCompare.
Gun slot, EQC sets a bunch of the INV_* global vars that used to be nil (I think they might be set now I'm not sure) so that it can getglobal() the strings returned by GetItemInfo() to figure out that all the different ones used by the ranged slot are the same. This was actually the cause of all the "Ace2 has been blocked from preforming a protected action" messages from using [equiped] in macros when TBC first came out because one of the C functions used by that option actually reads all those INV_* global vars. I moved all the 6 or so locale files for EQC into the main addon file so I could make that a local change instead of global to fix that. But it still had lots of issues back then before I switched to tekKompare and the only commit since then other than localizations was something specific to the atlasloot tooltips so nothing has been fixed.
Tell the Examiner author to fix his code so tekKompare works with it because hes obviously the one doing something different than every other author so theres no way in hell tekKompare will get code to work on his tooltips.
Also I'm pretty sure the ranged slot comparison in EQCompare is somewhat broken due to my fix a long time ago to prevent it from tainting and completely breaking some macro functions. And the size difference between EQCompare and tekKcompare doesn't have anything to do with features, its all about EQCompare being written for WoW 1.x and not using functions available by the default ui making it have to do all the calculations on what slot an item should be compared against and frankly very poor design of doing that because of the workarounds needed in WoW 1.x due to api inconsistances.
You don't want to know how hard I'm laughing about the complaint that tekKompare hasn't been updated since June 2007. Guess what EQCompare hasn't gotten an update other than translations and toc bumps for a year. It has lots of bad code that has not been updated for WoW 2.x and I'm not talking about minor little 'oh if I was to write this I would do it this way' stuff but serious 'needs to be rewritten for WoW 2.x because its incompatible' code. I put the toc interface number below 20000 so it wouldn't show up on the files.wowace.com listing anymore so new people won't install it. If you seriously want to keep using EQCompare then go ahead and edit the toc yourself, its not like you'll have to do it more than once since this addon is dead.
After I did a bit of diging to find the source of the tainting isuse with macro conditionals using [equipped] I found that EQCompare is flawed in its current design. Currently EQCompare scans the item tooltip for a string to determain which slot the item goes in but some of the strings it checks for are nil in the default UI. So the EQCompare localization files overwrote them, then 2.0 came around and tainting was introduced... yada yada yada... and now because somebody tainted a few INVTYPE_* variables when you put [equipped:*] in a macro you get an error message. In conclusion, teks new mod is much much better so everybody just use that instead.
(where did the spellchecking option on the forums go? its too damn earlyer in the morning to be checking my own spelling....)