I am definitely in favor of this change. The proposed behavior change is far more intuitive (in fact I always assumed aliases would override builtin functions just like commands) and certainly more consistent with other aspects of the language. Seeing as how now is the perfect time to break backwards compatibility... I say go for it. We don't expect all EPIC3 scripts to work with EPIC4 so we shouldn't expect all EPIC4 scripts to work with EPIC5 either. Remember, EPIC5 is considered a completely separate project; the "5" isn't a version number, it is part of the name. I think we need to be slightly less concerned about breaking scripts and more concerned with improving the client and the ircII language. EPIC4 is perfectly functional for those that want to resist change. I know I for one will be supporting an EPIC4 version of my script pack long into the future regardless of what happens with EPIC5.
-- Brian Weiss fudd @ EFNet http://www.epicsol.org/darkstar/ _______________________________________________ List mailing list [EMAIL PROTECTED] http://epicsol.org/mailman/listinfo/list
