#324 Unexpected error markers in `included files

[Chris Smith]

In version 1.5.6 of SVEditor, I'm seeing problems with included files when they are viewed in the editor whenever something other than a variable declaration is encountered. The attached example has a module called 'tb' thatincludes a file called 'inc.svh' that contains a simple initial block with a single $display in it. The problems window is empty, but there is an error marker on the initial line in inc.svh saying 'Invalid type name "initial"'.

It could be that there is some confusion when inc.svh is opened in the editor, and it is being interpreted as if it were a file that is being compiled directly with compilation-unit scope, not by being `included.

[Matthew Ballance]

Hi Chris,
SVEditor assumes that each file opened in the editor contains only top-level elements (eg class, module, package, variable declaration). SVEditor is able to parse file hierarchies that include file fragment, such as inc.svh. However, when a file is opened in the editor, the current assumption is that only top-level elements are present.
Is it very common in your environment to have SV fragments in included files?

Thanks,
Matthew

[Chris Smith]

Hi Matthew,
It's not very common that include fragments, most of the time it's entire classes/modules/etc. that are handled fine. Everything appears to get parsed correctly in the context of the including code, so I'm not too worried.
Thanks,
Chris.