On Thu, 2005-08-04 at 10:26 -0400, Ben Winslow <[EMAIL PROTECTED]> wrote: > Personally, I think you're not really gaining anything by doing this, but > you are losing something in breaking backwards compatibility. Consider > that, if you currently want to send /exec to the person you're talking to > in a query, you need to do /exec -m <querydestination>; with the change, > if you were talking in a query and wanted output to go to the channel, > you'd have to do /exec -m <channel> instead of /exec -o. Basically, I > don't see any net in making the change.
it's working more untuitively in all other `major' clients. i know many users who think of epic as a really backward client, coders should try and eliminate all not-so-well-thought features and core functionalities, so more people would consider using epic as a good alternative to irssi or xchat. introducing nonblocking connect() calls was a good idea, but there are many more which may discourage new users and scripters. IMHO it's a good approach to change old and unuseful behaviour in development branch. if it's going to include a change which will break each and every script, making the language in overall more feature-rich and intuitive, it's not really bad. -- Stanisław Halik :: http://weirdo.ltd.pl _______________________________________________ List mailing list List@epicsol.org http://epicsol.org/mailman/listinfo/list
