Super Prev Next

Configuring H2D

Super Prev Next

Setting up system search path

If you installed H2D as part of an XDS package, no additional setup is required. Otherwise you must tell your operating system where to find the executable before using H2D. Refer to the h2d.txt file from the on-line documentation.

Super Prev Next

Working configuration

The H2D working configuration includes an executable file and a set of system files: Search path redirection file
h2d.cfg Configuration file
h2d.msg Message file

Upon invocation, H2D tries to locate these files in the current directory and then in the directory where H2D executable resides. If a redirection file, is found, all other files are searched for/created using paths defined in it, otherwise the current directory is used for all input and output, except files specified with directories.

The configuration file contains various H2D settings. If the configuration file is not found, default settings are used.

The message file contains texts of error messages.

Super Prev Next

Redirection file

Upon activation, H2D looks for a file called --- the redirection file. This file defines directories in which all other files are searched for or created. A redirection file has to be placed in the current directory, otherwise the master redirection file from the directory where H2D executable resides is used.

A redirection file consists of several redirections:

Redirection = Pattern "=" directory {";" directory}

Pattern is a regular expression which all file names used by H2D will be compared with. A regular expression is a string containing certain special characters:

Sequence Denotes
* an arbitrary sequence of any characters, possibly empty
(equivalent to {\000-\377} expression)
? any single character
(equivalent to [\000-\377] expression)
[...] one of the listed characters
{...} an arbitrary sequence of the listed characters, possibly empty
\nnn the ASCII character with octal code nnn, where n is [0-7]
& the logical operation AND
| the logical operation OR
^ the logical operation NOT
(...) the priority of operations

A sequence of the form a-b used within either [] or {} brackets denotes all characters from a to b.

When H2D looks for or intends to create a file, its name is sequentially compared with all patterns from the top of the redirection file. A file is created in the first directory of the list corresponding to the matched pattern. A file is searched for in all directories in the list (from first to last) until it is found or the directory list is exhausted. If a match is not found, the file is created or searched for in the current directory. Note: If a match is found, the current direcory is not searched unless it is explicitly specified in the directory list.

It is possible to put comment lines into the redirection file. A comment line should be started with the % character.

Super Prev Next


*.h       = h; .; c:\bc\include
mac_*.def = macro;
*.def     = def;
mac_*.mod = macro;
*.h2d     = h2d;

Super Prev Next

Configuration file

The configuration file is used to set options which control various aspects of H2D behaviour: names of generated files, source/target language extensions, mapping of C base types to Modula-2 types etc. It should reside in the current directory or in the directory with H2D executable (the master configuration file). However, it is recommended to use a project file instead of a local configuration file to specify options for a particular set of header files.

An option is a pair (name, value). Every line in the configuration file may contain only one option setup directive. Arbitrary spaces are permitted. The % character starts a one-line comment. Option setup directives have the following syntax:

Option = "-" name ("-" | "+" | "=" (string | integer))

The same syntax is used for command line options and in a project file. Command-line options have the highest priority. Options specified in a project file override the configuration file settings.

Options, their meanings and valid values are described in Chapter Options Reference.

-DEFEXT  = def    % file extensions
-MODEXT  = d
-PRJEXT  = prj
-TREEEXT = inc
-DIREXT  = dir

-DEFPFX = h2d_    % prefix for output definition modules
-MACPFX = m_      % prefix for macro prototype modules

-BACKEND = COMMON % M2 compiler compatibility mode: C, NATIVE, COMMON
-GENMACRO-        % do not generate macro prototype modules
-GENWIDTH = 70    % maximum string length in output files
-COMMENTPOS = 0   % comment position
-CHANGEDEF+       % allow to overwrite existing definition modules
-PROGRESS+        % enable progress indicator
-CSTDLIB-         % do not set C standard library option
-CPPCOMMENTS+     % recognize C++ comments
-MERGEALL+        % merge all #included headers
-GENSEP-          % separate merged headers with comments
-GENLONGNAMES-    % prepen module name with directory names
-GENENUM = CONST  % enum transtaltion mode: CONST, ENUM, AUTO
-GENTREE+         % create file with include/merge tree
-GENDIRS+         % extract non-standrard directives
-GENROVARS+       % translate constants to read-only variables


-ctype = signed char        =  1, CHAR
-ctype = signed int         =  4,
  .  .  .
-ctype = long float         =  8, UNDEF
-ctype = long double        =  8, UNDEF


-m2type = INTEGER         = 4, SIGNED
-m2type = SHORTINT        = 1, SIGNED
  .  .  .
-m2type = SYSTEM.SET32    = 4, SET
-m2type =      = 4, SIGNED
-m2type = SYSTEM.unsigned = 4, UNSIGNED

Super Prev Next

Customizing H2D messages

The file h2d.msg contains error messages in the form

number text

The following is an excerpt from h2d.msg:

    001 Can't open file %s
       .  .  .
    010 Invalid use of modifier
       .  .  .

Some messages contain format specifiers for additional arguments. In the example above, the message number 001 contains a %s specifier which is substituted with a file name when the message is printed.

In order to use a language other than English for messages it is necessary to translate message texts, preserving error numbers and the number and order of format specifiers.