Implemented 005 prefix parsing

[Hello71]

No description provided.

[martynsmith]

Hi,

I had a read through your patch and it looked a little over-complex.

I re-implemented the 005 message parsing using a regexp (which seemed a little more straight forward) and then I heavily refactored the MODE event processing (because neither your implementation or the existing one worked correctly).

Hopefully it all looks okay to you now :-)

[Hello71]

Possibly better regexp:

/PREFIX=\(([a-z])\)([!@#$%^&*]*)/

Also, just so I don't have to look this up, the relevant section from Internet-Draft IRC RPL_ISUPPORT Numeric Definition:

The PREFIX parameter specifies a list of channel status flags (the
"modes" section) that clients may have on channels, followed by a
mapping to the equivalent channel status flags ("prefixes"), which
are used in NAMES and WHO replies. There is a one to one mapping
between each mode and prefix.

The order of the modes is from that which gives most privileges on
the channel, to that which gives the least.

[Example: (ab)&* maps the channel mode 'a' to the channel status
flag '&', and channel mode 'b' to the channel status flag '*'.]

[Example: PREFIX=(ohv)@%+ maps channel mode 'o' to status '@', 'h'
to status '%', and 'v' to status +.

The default value for PREFIX is "PREFIX=(ov)@+", which corresponds to
RFC 1459 [5]. It SHOULD NOT be specified if the server provides only
these modes. If a server provides ANY additional status flags, it
MUST also provide (ov)@+ (assuming they are applicable to the
server). The PREFIX parameter may be advertised with a null value
specifier; this indicates that no prefixes are supported by the IRC
server.

Note that PREFIX does NOT specify whether or not the server sends
multiple prefix characters for a user in NAMES replies.