Check Header files for incorrectly defined commands

[RobertvanderHulst]

Foxpro and other dialects use this format to specify a variable that has the name of for example a workarea

SELECT &cArea

We have a UDC #command SELECT <whatever> => DbSelectArea( <(whatever)> ) This does not work with the &cArea However this does:

#command SELECT <(whatever)> => DbSelectArea( <(whatever)> )

Se we have to make sure that the right match markers are used in the UDCs to also match & operations

Also some commands are defined with the wrong match markers:

This #command SET CONSOLE (<x>) => Set( Set.Console, <x> ) should be #command SET CONSOLE <(x)> => Set( Set.Console, <(x)> ) then it matches &SomeVar as well. Note that the parens are now inside the Less Than and Greater than and the result marker has parens too.