DVT e Language IDE User Guide
Rev. 24.1.10, 14 May 2024

6.3 Naming Conventions Checking

Many times naming conventions are established. For example each enumerated type definition should end with _t, each unit definition with _u or each type should be prefixed with vr_ahb.

Naming conventions are automatically checked when building a project. You just need to define them:

Right click on the project, choose Properties-> DVT -> Naming Conventions preference page.

Naming conventions can be shared using Settings Management. Managed naming conventions are not editable and are marked with gray color.

The conventions are identical if they have the same name and apply to the same language. In this case, the precedence is:

  • name checks defined in .dvt (the last defined convention has the highest priority)

  • name checks coming from $DVT_USER_SETTINGS/naming_conventions.xml

  • name checks coming from $DVT_COMMON_SETTINGS/naming_conventions.xml

Overridden naming conventions are marked with a strike out line.

Note: If no naming_conventions.xml file is present in the project's .dvt directory, default rules will be shown. They are not enabled and will not override any rule defined in $DVT_USER_SETTINGS or $DVT_COMMON_SETTINGS.

Naming convention violations are presented as warnings in the Problems View. You can show the Problems View from menu Window > Show View > Other... > General > Problems. Double clicking on some warning will jump to the source location.

Configuration File

You can edit manually edit naming convention by editing naming_conventions.xml file. It is located in .dvt folder.

A small example can be seen below:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE conventions PUBLIC "-//DVT//naming_conventions" "naming_conventions.dtd">
<conventions version="1">
<convention description="" enabled="true" kind="UNIT" language="E" match="POSITIVE" name="MY_CONVENTION">.*_u$</convention>
<convention description="" enabled="true" kind="METHOD" language="E" match="POSITIVE" name="ANOTHER_CONVENTION">.*_m$</convention>

For example, the first convention is for e Language, is named "MY_CONVENTION", is applicable for units and the pattern .*_u$ (the name of the unit must end with _u ) must match the name of every unit, else a warning will be triggered.