Calling xrun for Matlab and R COM automation client support

[Ecovi]

I am using Eviews's COM automation client support, but I am having doubts on the correct usage of xrun. The manual says:

"xrun should be followed by the command you wish to run, surrounded in quotes."

Which actually means (I think) that xrun expects a string as argument. However, xrun also works without quotes, which is easier to program because my execution commands are based on multiple program variables (strings and values). The necessity to add quotes would be cumbersome as you would have to concoct a string first based on these program variables, then pass the string to xrun. If it does not have to be passed as a string I can just use curly braces to expand my program variable names to specify the desired runnable command.

I'm just making sure I am not doing anything wrong. And if not, please correct the manual to reflect this feature.

[EViews Steve]

Technically, you don't need quotes if your command does not contain any spaces. To cover the case where the command does contain spaces, our manual states that quotes are needed (as using them all the time does not hurt).

[Ecovi]

Actually it also works for commands with spaces. They don't need quotes.
It also works when passing string objects or string variables containing spaces (also without the string containing quotes), expanded using curly brackets.