Spaces between function names and parameter lists cause 'Expected token? EOL' errors when the original Dragon Basic allowed it.

[supercom32]

Issue found using the latest version of Dragon Basic under Linux (Commit ID: d2ce042)

Spaces between function names and parameter lists cause 'Expected token? EOL' errors when the original Dragon Basic allows it. Ie: 'Sub myFunction (myParameter)' vs 'Sub myFunction(myParameter)'. This might be as-designed since the new DBC isn't supposed to be 100% compatible, but I thought I'd raise the issue ether way for confirmation and tracking purposes.