> This basically means you end up having to special case this (is there a
> colon? Then theres no part message. Is there no colon? Then theres a part
> message) which seems to be nothing but extra work.
Huh? You're confused. The RFC says that if there's a :, then all text
following the colon, ev
On Sunday 30 Mar 2003 1:39 pm, [EMAIL PROTECTED] wrote:
> And theres exactly the same `issue' for clients rejoining during a split -
> I forget which way around it is but a normal client join and a netsplit
> join are different - one is : prefixed, the other is not.
A lot of these problem
I never quite understood this - it USED to be the case that the message
looked like
PART #channel
or
PART #channel :Part message
Now its
PART :#channel
or
PART #channel :Part message
This basically means you end up having to special case this (is there a
colon? Then theres no part message. Is th
I had the same problem when using eembots,
fixed this in the source with some help :)
- Original Message -
From: "Mathieu Rene" <[EMAIL PROTECTED]>
To: "'Tom Laermans'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, March 29, 2003 4:54 PM
Subject: RE : [Coder-Com] Fwd: [Cservice]
