Command grouping broken?

[Charles Dye]

C:\>ver

TCC  21.01.55   Windows 7 [Version 6.1.7601]

C:\>( set foo=1 & set bar=2 )

C:\>set foo
1 & set bar=2

C:\>set bar
TCC: Not in environment "bar*"

C:\>

 

[vefatica]

It's OK in build 54. I have an ongoing project which relies heavily on command grouping. Should I update to build 55?

 

[Charles Dye]

On further study, I think this one affects specifically SET in command groups, not command groups in general.

 

[vefatica]

On further study, I think this one affects specifically SET in command groups, not command groups in general.

That's how I'm using it!

 

[vefatica]

That's how I'm using it!

And it is broken. :-(

 

[rconn]

Not command grouping per se; it's a problem with emulating some noxious CMD undocumented behavior (bug) with SET as the first command in a command group.

There is a workaround in 21.01.56 (which should be uploaded later today).

 

[Charles Dye]

And all for one batch file which exploits an obscure bug? Is the author given as "Outsider", by any chance?

 

[rconn]

Fixed in build 21.01.56 (already uploaded).

 

[Charles Dye]

21.0.56 looks much better; thank you.