Commands are parsed incorrectly if a command contains another valid command in its name.

[opendarkbasic]

Commands are parsed incorrectly if a command contains another valid command in its name.

[TheComet]

I'm unable to create a test case to reproduce this behavior. The following test passes:

TEST_F(NAME, command_name_inside_command)
{
    cmdIndex.addCommand(new cmd::Command(nullptr, "text", "", cmd::Command::Type::Void, {}));
    cmdIndex.addCommand(new cmd::Command(nullptr, "set text font", "", cmd::Command::Type::Void, {}));
    cmdIndex.addCommand(new cmd::Command(nullptr, "center text", "", cmd::Command::Type::Void, {}));
    cmdIndex.addCommand(new cmd::Command(nullptr, "wait key", "", cmd::Command::Type::Void, {}));
    matcher.updateFromIndex(&cmdIndex);
    ast = driver->parseString("test",
        "set text font \"Arial\"\n"
        "text 20, 20, \"Hello\"\n"
        "center text 200, 200, \"Centered\"\n"
        "wait key\n");
    ASSERT_THAT(ast, NotNull());
}

./odbc_tests --gtest_filter="db_parser_command.command_name_inside_command"
Note: Google Test filter = db_parser_command.command_name_inside_command
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from db_parser_command
[ RUN      ] db_parser_command.command_
[       OK ] db_parser_command.command_ (1 ms)
[----------] 1 test from db_parser_command (1 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (1 ms total)
[  PASSED  ] 1 test.

Can you verify that those 3 text commands are loaded?

./odbc --dump-cmd-names | grep text

[dgavedissian]

OK, now I'm very confused. I ran the --dump-cmd-names command, it dumped 1633 commands, and it appears that there are no "text" commands whatsoever, plus "ink foreground" and "ink background" is also missing. Perhaps it's not a parser problem then, will dig further.