forked from chipsalliance/verible
-
Notifications
You must be signed in to change notification settings - Fork 0
/
verilog_token.h
37 lines (31 loc) · 1.49 KB
/
verilog_token.h
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
// Copyright 2017-2020 The Verible Authors.
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
#ifndef VERIBLE_VERILOG_TOKEN_VERILOG_TOKEN_H__
#define VERIBLE_VERILOG_TOKEN_VERILOG_TOKEN_H__
#include "absl/strings/string_view.h"
#include "verilog/parser/verilog_token_enum.h"
namespace verilog {
// Returns token identifier suitable for use in string-based APIs (such as JSON
// export in verible-verilog-syntax). The identifiers are easy to type in
// programming languages and are mostly self-explanatory. They use:
// - Token text for string and character literal tokens. Examples:
// "module", "==", ";", "'"
// - Token name used in verilog/parser/verilog.y. This uses the original token
// names, not their (optional) display names. Examples:
// "SymbolIdentifier", "TK_DecNumber", "TK_EOL_COMMENT", "TK_NEWLINE"
//
// See also: verilog_symbol_name() in verilog_parser.h
absl::string_view TokenTypeToString(size_t tokentype);
} // namespace verilog
#endif // VERIBLE_VERILOG_TOKEN_VERILOG_TOKEN_H__