Check VHDL code for common codestyle problems.
Rules include:
Signals, variables, ports, types, subtypes, etc. must be lowercase.
Constants and generics must be uppercase.
Entities, architectures and packages must be “mixedcase” (may be 100% uppercase, but not 100% lowercase).
Ports must be suffixed using _i, _o or _io denoting its kind.
Labels must be placed in a separated line. Exception: component instantiation.
End statements must be documented indicating what are finishing.
Buffer ports are forbidden.
VHDL constructions of the “entity xxxx is” and similars must be in one line. You can’t put “entity xxxxx” in one line and “is” in another.
No more than one VHDL construction is allowed in one line of code.
See <http://fpgalibre.sourceforge.net/ingles.html#tp46> for more information.
Metadata
Release files for VHDLLintBear 0.10.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| VHDLLintBear-0.10.0.tar.gz | 2.5 kB | Details |
Release files / VHDLLintBear-0.10.0.tar.gz
| Download URL | VHDLLintBear-0.10.0.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
96d36ddab71f3dfaf7959a0ee5b825e120d4d49445525495830c9768903ef885
|
|
BLAKE2b-256 checksum How to use checksums |
5941d7d98daaec9e1abb0f2021faf5eef0095ad2d918855d92297eda08a7abb6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |