HCT - HCT environment. Provides global variables and subroutines.
If true then debug messages will be available.
Provides debugging parser.
This variable connects with yydebug parameter of the Parse::Yapp module,
where can be found more details.
Bit Value Outputs
0x01 Token reading (useful for Lexer debugging)
0x02 States information
0x04 Driver actions (shifts, reduces, accept...)
0x08 Parse Stack dump
0x10 Error Recovery tracing
If true, HCT will use threads.
The max number of threads.
Timeout for one thread.
If set, then all data will processed by this language.
List of file extensions and languages, which correspond to them.
file extansion ==> language name
If set, all files for processing will be located in a single list.
Keep a path to the current directory.
If true, HCT will process subdirectories recursively.
If true, HCT will process all target files and directories (systems, temporary, etc.).
Provides global Dumper subroutine from Data::Dumper.
Provides a standard of debug or error messages, that creates the HCT environment.
Produces an error message by using MESSAGE subroutine, then exit.
Produces a debug message (if DEBUG variable set) by using MESSAGE subroutine.
OO modules can use this subroutine to standardize the output messages. Standard example of using:
sub AUTOLOAD
{
return HCT::AUTOLOAD (
(caller),
our $AUTOLOAD,
@_
);
}
This document is part of HCT, the Hardware Complexity Tool.
Generated: Fri Jul 17 10:38:47 2009