Actually.. IS it possible for an ircd to send non-whois numerics between 311-318? I know it technically is, but I don't think I've ever come across any ircd implementation that could do this... a simple heuristic could cover the bases:
If an UNKNOWN numeric is sent between 311-318, assume it is part of whois
UNKNOWN being any numeric that is not already registered.
This will solve the problem in the future as IRCDs add more custom responses to WHOIS replies. AFAIK this is not the first time this issue has come up-- it happened previously with 338, right? Seems that it's likely to happen again, so there should be a more generalized solution here.
