Naoya Hatta

Thank you for your information! I checked the failed cases. * br_gh330.v This is caused by huge nested expression. I'll consider the way to fix it. * escaped_macro_name.v, pr1758122.v They...

I fixed the embedded single line comment issue.

In the LRM, event_control is defined as below: ``` event_control ::= @ hierarchical_event_identifier | @ ( event_expression ) | @* ... ``` This doesn't have space between `@` and `*`....

In the LRM, there are some sequential symbols not operator: ``` .* @@( block_event_expression ) ``` I think these can't be separated by space too. Additionally commercial tools don't support...

The "boldface-red" seems to have no special meaning. > This standard uses a minimal amount of color to enhance readability. The coloring is not essential and does not affect the...

In my understanding, BNF don't take care whether the sequence in definition is keyword, operator or token. It is only character sequence. For example. `"DPI-C"` is 7 sequential characters, and...

After discussion with my friends, I understand the problem is the missing of tokenize definition in LRM. Now I think like below: * `@*` is valid * `@ *` may...

I think whether each tool should cover de facto-standard functionality depend on the purpose of the tool. I agree that simulator is expected to support the functionality for usability, but...

I found the case in Accellera Mantis. https://accellera.mantishub.io/view.php?id=1286 The case say that the current BNF shows the space between `@` and `*` is not allowed and should be fixed. So...

ptags supports `-L` option like ctags. So the following command will search all the files under the current directory, and generate tags parallelly. ``` $ find . | ptags -L...