Re: bug ?

[Peter Zelezny <zed@linuxpower.org>]

On Sun, 7 Apr 2002 09:57:06 +0100
Andrew Suffield <asuffield@debian.org> wrote:

> > Peculiar. Andrew Suffield, are you still around? Any explanation from OPN
> > programmers?
> 
> config.h.opn:
> /* SANE_CASE_CONVERSION
>  * This causes {, }, |, and ~ to be considered different characters to [, ],
>  \, and ^*/
> #define SANE_CASE_CONVERSION
> 
> I refer you to the POSIX standards on case matching in the C locale.
> 
> This was done partly because the rfc1459 definition is stupid, and
> partly because the ~ character was reserved for another purpose (which
> will hopefully be completed and deployed in the near future), and
> justified by the behaviour of bahamut (since it doesn't seem to cause
> dalnet much of a problem).
> 
> I guess an entry in the 005 numeric for this is possible, but given
> the behaviour of ircnet on that one, the chances of getting everything
> changed aren't good; certainly I'm not going to waste time trying to
> talk sense into bahamut coders. If somebody can get dalnet to add a
> flag to their numeric, I'll include it in dancer for the sake of
> compatibility (but OPN's interest in maintaining compliance with
> rfc1459 is minimal; compatibility with rfc1459-like clients will be
> maintained to a reasonable level, but the intent is to move towards a
> saner protocol).
> 
> Meanwhile, might I suggest a config option in xchat? (preferably
> per-connection, if that's possible)

That would still require a server-dependant string comparision function.
I really don't want to put something like this in 50 odd places:

if (serv->breaks_rfc1459_strcmp)
	strcasecmp();
else
	rfc_cmp();

I understand it was a stupid decision for the original rfc to use that weird
scandinavian case conversion, but it's now set in stone. If you were designing
a new protocol, of course you'd go with a standard locale strcasecmp, but you
aren't. You arn't archieving anything positive by going with a non-1459
compare. Making the irc2 protocol more "clean" might sound nice, but you'll
just break compatability. Before long, numeric 005 will get so long, it'll
go over the 512 byte limit.

P.S. The "~" character isn't allowed in nicknames anyway.

-- 
Peter Zelezny. <zed@xchat.org>
--
XChat-discuss: mailing list for XChat users
Archive:       http://mail.nl.linux.org/xchat-discuss/