HCT.3pm

Langue: en

Version: 2009-08-08 (fedora - 01/12/10)

Section: 3 (Bibliothèques de fonctions)

NAME

HCT - HCT environment. Provides global variables and subroutines.

DESCRIPTION

GLOBAL VARIABLES

DEBUGGING

DEBUG
If true then debug messages will be available.
YYDEBUG
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
 
 

THREADS

USE_THREADS
If true, HCT will use threads.
MAX_THREADS
The max number of threads.
THREAD_TIMEOUT
Timeout for one thread.

HDL

FORCE_LANGUAGE
If set, then all data will processed by this language.
FILE_ASSOCIATIONS
List of file extensions and languages, which correspond to them.
         file extansion ==> language name
 
 

LISTING

BATCH
If set, all files for processing will be located in a single list.
START_DIR
Keep a path to the current directory.
LIST_RECURSIVELY
If true, HCT will process subdirectories recursively.
LIST_ALL
If true, HCT will process all target files and directories (systems, temporary, etc.).

GLOBAL SUBROUTINES

DUMP
Provides global "Dumper" subroutine from Data::Dumper.
MESSAGE
Provides a standard of debug or error messages, that creates the HCT environment.
ERROR
Produces an error message by using "MESSAGE" subroutine, then exit.
DEBUG
Produces a debug message (if "DEBUG" variable set) by using "MESSAGE" subroutine.
AUTOLOAD
OO modules can use this subroutine to standardize the output messages. Standard example of using:
         sub AUTOLOAD
         {
                 return HCT::AUTOLOAD (
                         (caller),
                         our $AUTOLOAD,
                         @_
                 );
         }