home *** CD-ROM | disk | FTP | other *** search
-
- NOTE: All the Ada source files are in the file called halstead.src,
- and all the documentation files are in the file called
- halstead.doc. All the test files are in the file called
- halstead.tst. These files can be broken apart using the
- WIS JPMO's tool Combine & Break (PD:<ADA.TOOLS>CBREAK*).
-
- Note: This version of HALSTEAD ignores the LIBRARY parameter. The
- directory containing the AIE program library must be your default
- directory when you run HALSTEAD. This is a limitation of the AIE
- Program Library Manager which should be corrected at some time in the
- future.
-
- To use the HALSTEAD tool you must:
-
- 1. Be a "HIF User". See the Byron/AIE Programmers Reference Manual
- for details. This requires that certain logical symbols be defined
- and that you have run the ADD_USER tool to make yourself known to
- the HIF database.
-
- 2. Define a symbol HALSTEAD so that VMS knows what executable to run
- when you type the HALSTEAD command. For example:
-
- $ HALSTEAD :== $USER1:[NOSC.TOOLS]HALSTEAD.EXE
-
- NOTE: The full path name of the executable is required in the
- definition of the symbol. The pathname given here is just an
- example and will be different on your system.
-
- 3. Create a Byron/AIE program library and use the Byron/AIE compiler
- front end to analyze source code into it. The AIEPLIB and AIECOMP
- commands are used respectively.
-
- 4. Enter a command with appropriate parameters. For example,
-
- $ HALSTEAD(("MY_PROG", "TEST.OUT"));
-
- Entering the command with no parameters gives a brief description
- of how to use the tool.
-
-
- To build the HALSTEAD tool:
-
- 1. Compile all the abstractions into a program library (see READ.ME in
- abstractions directory for details).
-
- 2. Compile everything named in the HALSTEAD.CO file into the program library
- containing the abstractions or a sublibrary whose parent library contains
- all the abstractions. HALSTEAD.CO lists file names in a correct
- compilation order.
-
- 3. Link HALSTEAD with the program library where everything was compiled.
- To do this using the DEC Ada compiler type:
-
- $ ACS LINK HALSTEAD
-
-
- Files contained in the HALSTEAD.SOURCE directory:
-
- BLOCK_U.SPC BLOCK_U.BDY COMLIN.SPC
- COMLIN.BDY DEFS.SPC COUNTYPE.SPC COUNT.SPC
- COUNT.BDY COUNTYPE.BDY DEFS.BDY HDB.SPC
- HDB.BDY SCTYPE_SP.SPC SCNAME_EX.SPC
- SCCONSTRA.SPC IHSUBTYPE.DAT OBJ.SPC OBJ.BDY
- IHSERIES_.DAT IHAGG_NAM.DAT SCCHOICE.SPC
- SCAGG_COM.SPC SCAGG_COM.BDY IHCASE_AL.DAT
- IHHANDLER.DAT SCSTM.SPC SCITEM.SPC
- SCALTERNA.SPC SCALTERNA.BDY IHBLOCK_S.DAT
- SRCUTIL.SPC SCBLOCK_S.SPC SCBLOCK_S.BDY
- IHINNER_R.DAT SCCHOICE.BDY SCCOMP_UN.SPC
- SCCOMP_UN.BDY SCGENERAL.SPC SCCONSTRA.BDY
- IHVARIABL.DAT IHTYPE_DE.DAT ID_UTILS.SPC
- ID_UTILS.BDY SCDEF_ID.SPC SCDEF_ID.BDY
- SCGENERAL.BDY IHGENERIC.DAT SCGENERIC.SPC
- SCGENERIC.BDY SCHEADER.SPC SCHEADER.BDY
- SCVARIANT.SPC SCINNER_R.SPC SCINNER_R.BDY
- IHTASK_DE.DAT SCPKG_DEF.SPC SCOBJECT_.SPC
- SCSUBP_DE.SPC SCITEM.BDY SCITERATI.SPC
- SCITERATI.BDY SCNAME_EX.BDY SCOBJECT_.BDY
- SCPKG_DEF.BDY SCSTM.BDY SCSUBP_DE.BDY
- SCTYPE_SP.BDY SCVARIANT.BDY SRCUTIL.BDY
- HALSTEAD.ADA
-
-
- To change the assignemnt of a token as either an operator, operand, or
- neither, see COUNT.BDY. To change the computation of any of the HALSTEAD
- measures, see HDB.BDY. The file HALSTEAD.ADA contains the driver program.
-
-
- To test the HALSTEAD tool, create an AIE program library using AIEPLIB,
- compile [.TEST]SCANNERS.SPC and [.TEST]SCANNERS.BDY into the AIE program
- library using AIECOMP, make that library your default directory, and run
- HALSTEAD, as follows:
-
- $ AIEPLIB [.DEMOLIB]
- $ AIECOMP SCANNERS.SPC [.DEMOLIB]
- $ AIECOMP SCANNERS.BDY [.DEMOLIB]
- $ SET DEFAULT [.DEMOLIB]
- $ HALSTEAD(("SCANNERS"), "SCANNERS.OUT");
-
- Then, verify that the file SCANNERS.OUT is the same as that shipped with
- this release.
-