Forums Bug Reports setting variables to ""

when setting a variable to something that evaluates to "" at runtime, the variable is set to $null instead.
not necessarily a bug, i know, but i find the current behaviour misleading.

the following statement:
would set %x to $null if $1 is "", instead of setting it to "", as one would expect.
i think setting the variable to $null instead of "" should only be used in straightforward statements like:
because it expresses the intention of setting the variable to $null, unlike when setting a variable to something that evaluates to "". especially when used in the form shown, i don't think the variable should be set to $null, because it would be like it's evaluating the expression twice.

using mirc v6.16.

"" is concidered by most languages, including mIRC to be $null.

" " being a space.

Eamonn.

what if i just want to copy some text in a variable, literally. and this text happens to be "". that's not the same as $null to me. with the current behaviour i'd be forced to check if this text is "", then set it in some alternate way etc...

and the following statement:
sets %x to " ", not to a space. the behaviour only occurs with "".

In which case you would be screwed and have to check to be sure.

Eamonn.

While it's not really a solution, /hadd and /bset do not have this limitation.