I agree with /braw, or as I suggested /raw with a -b flag to treat &binvars specially.

This should be very possible. I wouldn't use the word 'evaluate' but rather 'print' the data contained in the &binvar at the point which &binvar appears in the string. This would require some secondary evaluation layer the same that $* exploits with `~$*

I also support the idea that all events and aliases should have &rawmsg and either &1 &2 &3 etc, or simply &params. I believe &1 &2 &3 may be unnecessary considering these would be space-delimited like their $1 $2 $3 counterparts... which means stripping any padded spaces. &1- or &params should be the only necessary binary sibling, for ease and sanity sake.

/bdo on the other hand, may be a tad too difficult for Khaled to impliment globally that supports all commands. Every command uses its parameters differently, /bdo could only really be useful for server-output commands (which /braw will already handle), or file-output commands (/bwrite), or screen-output commands... which should be /becho.

And yes, all of these uses only data up to the first NULL character should be printed... and in most cases, only up to the first CR or LF. Any following data is ignored.

Unfortunately, whenever I suggest any of these in the past... people still fixate on mIRC's current inability to handle &binvars... so I would like to re-iterate that these suggestions are FOR mIRC's expanded handling of &binvars.

- Raccoon

Well. At least I won lunch.
Good philosophy, see good in bad, I like!