this is probably a consequence of its special handling of variable names. much like the variable related commands, /sockread needs to be able to prevent evaluation of a %var if it appears as the first token of the <%var|&binvar> parameter. however, what we see here is that the tendency to not evaluate variables extends to the last potential evaluation of a variable in that token, even if it is contained within an identifier (except $eval() or $iif() to name a couple). i don't see why this extra handling exists, but it could just be due to recycling of code - who knows :P
you shouldn't evaluate the variable twice with $eval(%variable, 2), a simple $eval(%variable) or $(%variable) will suffice. it also appears that mIRC will evaluate the variable it's been 'saving' to leave escaped if there is a token after the <%var|&binvar> parameter, so 'sockread & $+ %var a' works as you need. but stick to the first solution ;P
