Use the correct type names for forward-declared parser types

This allows using the types in cxx bridges other than the ones that define
them.
This commit is contained in:
Johannes Altmanninger 2023-03-04 03:17:34 +01:00
parent b92313b79d
commit 494f10a5a8

View File

@ -37,7 +37,7 @@ struct SourceRange {
}; };
using source_range_t = SourceRange; using source_range_t = SourceRange;
enum class parse_token_type_t : uint8_t { enum class ParseTokenType : uint8_t {
invalid = 1, invalid = 1,
string, string,
pipe, pipe,
@ -51,8 +51,9 @@ enum class parse_token_type_t : uint8_t {
tokenizer_error, tokenizer_error,
comment, comment,
}; };
using parse_token_type_t = ParseTokenType;
enum class parse_keyword_t : uint8_t { enum class ParseKeyword : uint8_t {
none, none,
kw_and, kw_and,
kw_begin, kw_begin,
@ -73,13 +74,15 @@ enum class parse_keyword_t : uint8_t {
kw_time, kw_time,
kw_while, kw_while,
}; };
using parse_keyword_t = ParseKeyword;
enum class statement_decoration_t : uint8_t { enum class StatementDecoration : uint8_t {
none, none,
command, command,
builtin, builtin,
exec, exec,
}; };
using statement_decoration_t = StatementDecoration;
enum class parse_error_code_t : uint8_t { enum class parse_error_code_t : uint8_t {
none, none,