glossary.txt

STLstlfilt.zip

=============================================================================
STL Error Message Decryptor for visual C++
==============================================================================

Written by  Leor Zolman
            [e-mail]
            www.bdsoft.com
            STLFilt web page: www.bdsoft.com/tools/stlfilt.html

========
Glossary
========

I use several specific terms to refer to components of the STL filter
package and the various states that they can be in. Here are the key terms:

Proxy CL:    The CL.EXE obtained by compiling CL.CPP. After renaming the
             native MSVC CL.EXE to CL2.EXE, you install the Proxy CL 
             (named CL.EXE) by copying it to the native MSVC's bin directory.

Native CL:   The CL.EXE provided as part of the MSVC distribution. For use
             with the Proxy CL, the native CL should be renamed to CL2.EXE.

Installed:   When I speak of the Proxy CL being "installed", that means that
             the CL.EXE seen by the MSVC IDE (or the command processor if
             you're working from the command line) is the Proxy CL. When the 
             Proxy CL is installed, filtering may be enabled or disabled 
             (see below).

Uninstalled: When the Proxy CL is "uninstalled", then the CL.EXE seen by the
             IDE (or command processor) is the *native* CL.EXE (from the MSVC
             distribution, usually in the ...\VC98\bin directory). In this 
             state, the STL filter system is completely out of the picture.

Enabled:     When filtering is "enabled" (signified by the filter toggle file
             having an extension of ".ON"), then the Proxy CL performs error
             filtering for files with the appropriate extensions (as configured
             in CL.CPP)

Disabled:    When filtering is "disabled" (signified by the filter toggle file
             having an extension of ".OFF"), the Proxy CL *never* filters any
             error messages through the Perl script. Instead, the Proxy CL
             just hands control directly to the native CL.

Active/      STLTask.EXE installs/uninstalls the Proxy CL by copying files. 
Inactive:    The Proxy CL is "active" when CL.STL (actually, the value of
             the STLTask.CPP program variable proxy_cl_uninstalled_fname,
             but don't change it unless you have a very good reason to) 
             has been copied to CL.EXE (I also refer to this as the 
             *installed* state of the Proxy).  The Proxy CL is "inactive" 
             (*uninstalled*) CL.EXE is a copy of CL2.EXE.

             The native CL is "active" when CL.EXE is a copy of CL2.EXE.
             In this state, the Proxy CL would be inactive (uninstalled).
             The native CL is "inactive" when it only exists as CL2.EXE 
             (actually, the value of the program variable std_cl2_fname,
             but again, you probably won't need to change it). In this 
             state, the Proxy CL would be active (installed).