<P> parses as the erroneous construct: </P> <P> Similarly, if% foo% contains abc def, then a different syntax error results: </P> <P> The usual way to prevent this problem is to surround variable expansions in quotes so that an empty variable expands into the valid expression IF "" = = "bar" instead of the invalid IF = = bar . The text that is being compared to the variable must also be enclosed in quotes, because the quotes are not special delimiting syntax; these characters represent themselves . </P> <P> The delayed! VARIABLE! expansion available in Windows 2000 and later may be used to avoid these syntactical errors . In this case, null or multi-word variables do not fail syntactically because the value is expanded after the IF command is parsed: </P>

File extensions that can be run from the command prompt