Ken Domino

> @kaby76 I tested this branch with high success rate, the only tests which fail so far for me: > > ```c++ > std::unique_ptr test; > std::array test; > ```...

Looks like some problems with basic types. `std::array test;` not accepted, but `std::array test;` is fine.

I tried adding the basic types ("long", "int", etc) to unqualifiedId. This "takes care of" parsing the several new problems you mentioned, e.g., `std::array test;`. But, this also causes some...

I do have a preprocessor that is generated from the preprocessor. g4 grammar. I haven't added it yet. I think I was trying to figure out how to integrate it...

@teverett This PR is ready. I entered a couple of Issues for things I uncovered while fixing this issue. We'll take care of those issues later. https://github.com/antlr/grammars-v4/issues/4152 https://github.com/antlr/grammars-v4/issues/4151

> @kaby76 Just a notice: while I don't know the grammar you are using (you were referring to openstd before), I was able to fix these issues above using [this...

There are several problems here with the rules that implement operator precedence. It was not implemented correctly for `a_expr_compare` and `a_expr_at_time_zone`.https://github.com/antlr/grammars-v4/blob/97bd28855acf37204623a71eb9d5ce3f9f62f80a/sql/postgresql/PostgreSQLParser.g4#L3669-L3671 For some reason, the person who implemented this seemed...

Yes, that is also a source of ambiguity. For [union10.sql](https://github.com/antlr/grammars-v4/blob/3f8074f7730c272ddfd2d77df0ae83b46422fd98/sql/plsql/examples/union10.sql), the ambiguity trees are: ``` subquery.sql.d=2441.a=5: (sql_script (unit_statement (data_manipulation_language_statements (select_statement (select_only_statement (subquery (subquery_basic_elements (query_block (SELECT "select") (selected_list (select_list_elements (expression (logical_expression...

This cannot be done. It is impossible to know which strings are actually dynamic sql statements. Further dynamic sql strings can be constructed.

Please edit your above comment to use [Fenced Code Blocks](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#fenced-code-blocks) around your code so we can see and copy the example using a simple click instead of select, then copy.