buf is a pointer to your "local per-socket buffer", which is filled up to len, which builds your "recieve queue" your recieve queue is iterated for cr, lf, or crlf with use of -n.
Exactly. Therefore, there is no need for mIRC to allocate a binvar with space for the cr/lf in order to get the cr/lf out of the socket buffer. It can simply discard the cr/lf, since they're no longer pending on the socket anyway. If the opposite of that was not what you were trying to argue in your first post, then I'm at loss as to what point you were trying to make there.
from position 1 to position <cr,lf,or crlf> is copied onto your binvar [..] Albiet these are now 0, instead of 13 and 10
You are describing
what is happening in the current mIRC version. I don't see anything in your post that explains
why this is desirable behavior rather than a bug. The fact that one could potentially make a script that relies on such broken behavior is rather besides the point.
