i think the issue here is, if they come 'packaged' in the installer, it can be argued that mIRC would therefore be supporting those addons in some way shape or form. Now, from here on in, Khaled has had a very tight watch on everything that goes into his program, as the only developer on the project (besides Tjerk for the help file documentation). The problem with supporting these addons is that, as with any addon from an anonymous source, you really can't guarantee the stability of those addons (in future versions). You can say that Khaled is a bit of a control freak here, with reason. The more addons you have in a program from different sources, the higher the risk of another exploit in the program-- something he surely does not want. Sure, Khaled can mess up and put bugs into his own program, but atleast he knows that who is responsible, etc. There is therefore really no need to go through the headache of a possible 'mishap', when the other option is very simple: Allow the user to find/install the addons himself, releasing [most of] the responsibility of a faulty script from the hands of Khaled himself. And this solution is very simple indeed with things like search engines.


- argv[0] on EFnet #mIRC
- "Life is a pointer to an integer without a cast"