@ DESCRIPTION: DCL utilities for generating code review materials.  E     MAKE_LISTING.COM	generate line-numbered listings and (optionally)  			  Difference listingsH     DOUBLE_CBAR.COM	combine change-bar Difference listings for same fileK     INDEX_LABELS.COM	generate table of contents and index of labels in file      USAGE:  G     To get brief help about how to use any of these procedures, execute B     the procedure and give it a question mark (?) as its P1 value.  C     Suppose that you are working on revisions to STUFF.MAR. In your E     working directory, you have a copy of the current STUFF.MAR. Your D     original proposal is in the same directory as STUFF_NEW.MAR; butH     in code review on it, several changes were suggested, which you needD     to take to a follow-up code review. You named the latest version     STUFF_FINAL.MAR   -     $ @MAKE_LISTING STUFF.MAR STUFF_FINAL.MAR    	The output files you get are   A 	    STUFF*.NLIS                 line-numbered listings of source ; 	    STUFF_FINAL.DIFF            regular Difference listing < 	    STUFF_FINAL.DIFF_PAR        parallel Difference listing> 	    STUFF_FINAL_BOTH_CBAR.NLIS  change-bar Difference listing  1     $ @MAKE_LISTING STUFF_NEW.MAR STUFF_FINAL.MAR   A 	You get a similar set of output files, but these compare the two * 	sets of proposed revisions you have made.  E     Each change-bar Difference listing (*CBAR.NLIS) from MAKE_LISTING J     begins with a change-bar listing of the "old" file (P1), and ends withI     a change-bar listing of the "new" file (P2). Using an editor, extract H     the portion of each *CBAR.NLIS file that is for the "new" file. TrimH     off the trailing summary of Difference statistics. For this example,%     assume you save these extracts as    	    STUFF_CBAR_ALL.NLIS 	    STUFF_CBAR_LATEST.NLIS   ?     $ @DOUBLE_CBAR STUFF_CBAR_ALL.NLIS STUFF_CBAR_LATEST.NLIS -        STUFF_CBAR_DOUBLE.NLIS  @ 	The two files input to DOUBLE_CBAR are identical except for theC 	locations of their change bars. One has change bars for lines that C 	differ from the original. The other has change bars for lines that 5 	differ from what you took to your first code review.   D 	The output file uses two different change bar symbols, one for eachE 	of the two sets of differences you want to show. A line that changed F 	at both stages of your development cycle has both change bars. A lineF 	that changed at only one stage of your development cycle has only the. 	type of change bar associated with its stage.  #     $ @INDEX_LABELS STUFF_FINAL.MAR   C 	To help everyone find their way through printouts in a code review ) 	meeting, this generates some handy files   & 	    STUFF_FINAL.TOC	table of contents+ 	    STUFF_FINAL.IDX	sorted index of labels    DETAILS:  L     The Difference listings generated by MAKE_LISTING and DOUBLE_CBAR ignoreG     blank lines, case, form feeds, spacing and trailing spaces. Ignored K     characters are included in the output, but ignored blank lines are not.    ORIGINS AND EVOLUTION:  I     Two of these tools were inherited from Bob Grosso. All of these tools L     were created for use in reviewing DCL procedures. However, they are alsoG     useful with other types of source code (except that INDEX_LABELS is G     helpful only when labels are distinguished by a colon as a suffix).   J     It is not my intention to enhance these tools further. If someone elseC     wishes to enhance them or add to the set, that is fine with me.   
 SUBMITTER:  $     Bonnie D. Huval				(02-May-1996)     STAR::HUVAL 