Unnecessary quotation marks in names when using IUTILS_name_to_string

[Ev3nt]

IUTILS_name_to_string contains a call to KEYWORD_stringIsAToken, which is triggered by any keyword, even if it is not actually needed. For example, when calling SHOW SYSTEM FUNCTIONs RDB$BLOB_UTIL.SEEK; we expect the following output:

Engine: SYSTEM
Parameters:
OUTPUT (RDB$INTEGER) INTEGER
HANDLE                            INPUT (RDB$BLOB_UTIL_HANDLE) INTEGER
MODE                              INPUT (RDB$INTEGER) INTEGER
OFFSET                            INPUT (RDB$INTEGER) INTEGER

However, we end up with the following output:

Engine: SYSTEM
Parameters:
OUTPUT (RDB$INTEGER) INTEGER
HANDLE                            INPUT (RDB$BLOB_UTIL_HANDLE) INTEGER
MODE                              INPUT (RDB$INTEGER) INTEGER
"OFFSET"                            INPUT (RDB$INTEGER) INTEGER

I have investigated the code, and this is happening because the word OFFSET is included in ParserTokens.h, which is causing this issue. Similar triggers occur with other keywords.

For example, if you call SHOW SYSTEM PROCEDURE RDB$BLOB_UTIL.CANCEL_BLOB;, you should see:

Engine: SYSTEM
Parameters:
BLOB                              INPUT (RDB$BLOB) BLOB CHARACTER SET NONE
=============================================================================

However, in the end we get:

Engine: SYSTEM
Parameters:
"BLOB"                              INPUT (RDB$BLOB) BLOB CHARACTER SET SYSTEM.NONE
=============================================================================

[Ev3nt]

PR: #8742

[sim1984]

What is the benefit of this change? On the contrary, using quotes allows you to copy the parameter for its actual use.

[sim1984]

select RDB$BLOB_UTIL.IS_WRITABLE(BLOB => '') as b
from rdb$database;

Statement failed, SQLSTATE = 42000
Dynamic SQL Error
-SQL error code = -104
-Token unknown - line 1, column 34
-BLOB

vs

select RDB$BLOB_UTIL.IS_WRITABLE("BLOB" => '') as b
from rdb$database;

      B
=======
<false>