"Set" command behavior - a bug?

[Progressor]

The documentation says:

If you enter only name, and there is no variable with that name, SET will display all environment variables whose names begin with name. For example, if there is no variable pa, the command below will display all variables whose names start with pa:

set pa

The above command is equivalent to the command

set pa*

Here is the batch file to test this:

set var1=var1
set var11=var11
set var1

The TCC output:

The cmd.exe output:

Does it look like a bug?

 

[Charles Dye]

TCC's behavior matches the documentation, so I would say no. More like a deliberate incompatibility.

(I'm guessing, but this behavior may go back to 4DOS, predating CMD.EXE.)

 

[AnrDaemon]

If you want to see the contents of a variable, use echo.
"Set" is to SET the variable.
All other behavior is undefined and cannot be relied upon across various shells.

 

[rconn]

This is WAD - TCC (4NT) had this feature long before CMD. When CMD added this, we decided (based on user feedback) to not emulate CMD's behavior of returning multiple values if there was an exact match.