Difference between revisions of "Escaped identifiers in RTL files and in Verific data structures"
From Verific Design Automation FAQ
| Line 5: | Line 5: | ||
No escaped identifier | No escaped identifier | ||
| − | In netlist outputs and in pretty-print outputs, identifiers are escaped based on the naming rules of the language | + | In netlist outputs and in pretty-print outputs, identifiers are escaped based on the naming rules of the language of the output file. |
'''Verilog:''' | '''Verilog:''' | ||
| − | starts with a backslash and ends with a space character | + | starts with a backslash and ends with a space character. |
The escaping characters '\' and ' ' are not part of the name. 'foo' is the same object as '\foo ' | The escaping characters '\' and ' ' are not part of the name. 'foo' is the same object as '\foo ' | ||
Revision as of 15:15, 16 March 2021
>>> This page is under construction <<<
Verific data structures:
No escaped identifier
In netlist outputs and in pretty-print outputs, identifiers are escaped based on the naming rules of the language of the output file.
Verilog:
starts with a backslash and ends with a space character.
The escaping characters '\' and ' ' are not part of the name. 'foo' is the same object as '\foo '
With AddSignal() when you define the name, you don't need to escape it.
But when you refer to an escaped id, you need to escape it.
VHDL:
enclosed in a pair backslashes. The backslashes are part of the name.
'\foo\' and 'foo' are too different objects
