Sigasi Studio 3.8 brings support for Markdown in Comments and for Multiline trailing comments. We also improved the Documentation Generation and the Dependencies View. Read below to find more new and noteworthy changes.
VHDL and SystemVerilog comments are now processed with a Markdown processor. This allows to add markup (e.g. bold, code, paragraphs, hyperlinks,…) to comments. This results in nicer hovers and documentation.
In hovers the complete Markdown syntax is supported. For PDF documentation generation following features are supported:
- paragraphs (add and empty comment line to break paragraphs)
- line breaks (by adding two trailing spaces)
- emphasis (
- strong (
- external links and email addresses (
Sigasi Studio has a few simple rules to associate comments with HDL declarations. In version 3.8 we have refined and extended the association rules to support multiple single line trailing comments.
Empty lines between comments now break the comment blocks. This provides a convenient way to un-associate comments from declarations. You can add an empty comment line to combine comments with multiple paragraphs.
We have also updated the Formatter and Structural select to respect (and fix) comments according to the new association rules.
Note that the comment association rules are identical for both (System)Verilog and VHDL.
We also did significant improvements to the documentation export:
- Support for (System)Verilog modules: The documentation now also documents (System)Verilog modules.
- Top Level only export: In the export wizard you can now select either a Project or just a top level. Selecting a top level will only add the documentation of design units that are part of the selected hierarchy.
- State machines: If architectures contain state machines, these will be included in the documentation
- Result folder: The generated
sigasi-docfolder (and no longer in the root of your project).
- Diagram paths: Diagrams are now generated in
- Duplicate design units: If your project contains duplicate design units, documentation export is not possible. We now show a clear dialog instead of a cryptic message in the console view.
The Dependencies Viewer can now also show the libraries in which files are built and it can show the design units within the files. Use the new icons to enable or disable the features of the Dependencies Viewer:
- Show all files in project
- Show libraries
- Show design units
- We implemented the last missing VHDL 2008 features in Sigasi Studio: functions with generic parameters
- Quickfix for c-style equals
- Improved autocomplete priorities (
records > conversion functions)
- Allow (System)Verilog Preprocessor settings dialog to globally include files
- Updated Eclipse in standalone version to Eclipse 4.7.2
- Added VHDL autocomplete template for
functionprototypes (useful in packages)
- Add parameter to
procedure bodyautocomplete template
- [XL] Added extra linting check for file header comments: check that header comment matches a pattern
- [XL] Added extra linting check for file names: check that the primary unit names in the file are part of the file name. Note that this check is ignored by default. You can enable it in the VHDL Errors/Warnings preference page (Style Validation > Filename must contain primary name)
- ticket 4099 : Wrong error message in pop-up when all licenses are in use
- ticket 4138 and 4019 : Rename refactoring
- ticket 4184 : [VHDL] Duplicate design unit markers occur multiple times
- ticket 4160 : [VHDL] Sort associations mangles up bit string literals (
- ticket 3813 : Rename in autocompletes steals enter keystroke from QF
- ticket 4070 : [VHDL] Undo is incorrect after rename refactoring with format on save
- ticket 4046 : Block Diagram: Entity instantiation without ports is displayed as unknown
- ticket 4036 : Vivado integration is missing VHDL (2008) version parameter
- ticket 4037 : [VHDL] incorrect duplicates declaration error for vhdl 2008 package instantiations
- ticket 4102 : [VHDL] Check for missing procedure implementation in protected types
- ticket 4049 : [(System)Verilog]
globalnot accepted as package name
- ticket 4048 : [(System)Verilog] Imports with
globalkeyword are not recognized
- ticket 4120 : [VHDL] Alias for package
- ticket 4185 : [VHDL 2008] allow local package instantiations in processes
- ticket 4194 : [(System)Verilog] Missing Questa
vlogerrors in the Problems View
- ticket 4219 : Issue launching