home *** CD-ROM | disk | FTP | other *** search
/ Simtel MSDOS 1992 June / SIMTEL_0692.cdr / msdos / dbase / dfixup36.arc / DFIXUP.PRN < prev    next >
Encoding:
Text File  |  1988-05-26  |  15.2 KB  |  316 lines

  1.  
  2.  
  3.  
  4. dFIXUP 3.6_________________________________________________________ May 25, 1988dFIXUP 3.6_________________________________________________________ May 25, 1988
  5.  
  6.  
  7.             NAME:     DFIXUP.EXE            NAME:               
  8.             
  9.             PURPOSE:  Processes standard dBASE1-type program files,            PURPOSE:                                                                                             _                    
  10.                       and writes properly indented output files. In
  11.                       addition,  dFIXUP   detects  and  reports  on
  12.                       programming mistakes,  and displays some file
  13.                       statistics.
  14.             
  15.             SYNTAX:   DFIXUP [filespec1 ... filespecN]            SYNTAX:                                   
  16.             
  17.                       filespec can be one of the following:
  18.             
  19.                            The name  of a  .PRG file, with optional
  20.                            .PRG extension.
  21.                            
  22.                            The name  of a  .CLP file  (used by  the
  23.                            Clipper2 compiler),  with optional  .CLP                                  _                                
  24.                            extension.  All   .CLP  files   must  be
  25.                            prefixed   with   an   '@',   which   is
  26.                            consistent with  the syntax  used by the
  27.                            Clipper compiler. .CLP files contain the
  28.                            names of  files  to  be  processed,  one
  29.                            filename per  line, with  optional  .PRG
  30.                            file extension.
  31.                            
  32.                       The dFIXUP  command line  supports both  path
  33.                       names and wildcards.
  34.                       
  35.                       If  no  command  line  arguments  are  given,
  36.                       dFIXUP will  prompt you  for an input file to
  37.                       be processed.
  38.                       
  39.                       For files  not prefixed  with an  '@', dFIXUP
  40.                       will  automatically   assume  a   .PRG   file
  41.                       extension. For  all files  prefixed  with  an
  42.                       '@', a .CLP extension is assumed. If you have
  43.                       a file  (either  .CLP  or  .PRG)  without  an
  44.                       extension, you  can process it by including a
  45.                       period after  the filename,  e.g. in  essence
  46.                       saying that the file extension is blank.
  47.                       
  48.                       
  49.             USAGE:    dFIXUP will  write all  .PRG files  specified            USAGE:                                                 
  50.                       into files  with the  same basename, but with
  51.                       an .OUT extension. The following are examples
  52.                       of some input file names, and their resulting
  53.                       output file names:
  54.             
  55.                            PAYROLL        PAYROLL.OUT
  56.                            SAMPLE.PRG     SAMPLE.OUT
  57.                            C:\DBASE\TEST  C:\DBASE\TEST.OUT
  58.             ____________________
  59.             1    dBASE is a registered trademark of Ashton-Tate            _                                                  
  60.             2    Clipper is a registered trademark of Nantucket            _                                                  
  61.  
  62.  
  63.  
  64. User's Guide ____________________________________________________________ Page 1User's Guide ____________________________________________________________ Page 1
  65.  
  66.  
  67. dFIXUP 3.6_________________________________________________________ May 25, 1988dFIXUP 3.6_________________________________________________________ May 25, 1988
  68.  
  69.  
  70.             
  71.                       All  specified  files  will  be  indented  as
  72.                       required, and comments will not be removed.
  73.             
  74.                       If you do not specify one or more files to be
  75.                       processed on  the command  line, dFIXUP  will
  76.                       ask you for the name of a single .PRG file to
  77.                       be processed.  In this interactive mode, both
  78.                       path names  and  .CLP  files  are  supported,
  79.                       while wildcards are not.
  80.             
  81.                       In addition  to the input file name, you will
  82.                       also be  asked to  supply an output file name
  83.                       (which must be different from the input file;                             ____                                  
  84.                       if this  is not the case, the input file will
  85.                       be destroyed),  as well  as whether to indent                         _________                                 
  86.                       the file  and whether  or not  to remove  all
  87.                       comment lines.
  88.             
  89.                       If you  press ENTER  without  a  filename  in
  90.                       response to  the output  file prompt,  dFIXUP
  91.                       will assume  the basename  of the  input file
  92.                       with an .OUT extension.
  93.             
  94.                       If  you   answer  'N'  to  the  prompt  about
  95.                       indenting, dFIXUP will remove all indentation
  96.                       from the  output file  specified. This can be
  97.                       useful after  development  is  complete,  and
  98.                       disk space is tight.
  99.             
  100.                       If  you   answer  'Y'  to  the  prompt  about
  101.                       indenting, or  if you  process files from the
  102.                       command line, dFIXUP will prefix each line of
  103.                       your program  with three spaces each for each
  104.                       level  of   indentation.  This  is  also  the
  105.                       default if  you press  ENTER in  response  to
  106.                       this prompt.
  107.             
  108.                       If  you   answer  'Y'  to  the  prompt  about
  109.                       removing comments,  dFIXUP  will  remove  all
  110.                       lines that start with a single asterisk ('*')
  111.                       or the  keyword NOTE.  dFIXUP will not remove
  112.                       comment lines  starting with  two  ampersands
  113.                       ('&'). Pressing  ENTER in  response  to  this
  114.                       prompt is equivalent to pressing 'N'.
  115.             
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127. User's Guide ____________________________________________________________ Page 2User's Guide ____________________________________________________________ Page 2
  128.  
  129.  
  130. dFIXUP 3.6_________________________________________________________ May 25, 1988dFIXUP 3.6_________________________________________________________ May 25, 1988
  131.  
  132.  
  133.             ERRORS:   dFIXUP will  detect the  following  kinds  of            ERRORS:                                                
  134.                       errors:
  135.             
  136.                       Mismatched statements:
  137.             
  138.                            IF - ELSE - ENDIF
  139.                            DO WHILE - ENDDO
  140.                            DO CASE - CASE - OTHERWISE - ENDCASE
  141.                            FOR - NEXT
  142.                            
  143.                            Example:
  144.                            
  145.                                 DO WHILE .T.
  146.                                    DO MAINMENU
  147.                                 ENDIF
  148.                            
  149.                       Unbalanced statements:
  150.                       
  151.                            IF - ENDIF
  152.                            DO WHILE - ENDDO
  153.                            DO CASE - ENDCASE
  154.                            FOR - NEXT
  155.                            
  156.                            Example:
  157.                            
  158.                                 IF AT(ANSWER,'YyNn') > 0
  159.                                    IF UPPER(ANSWER) = 'Y'
  160.                                       ...
  161.                                    ELSE
  162.                                       ...
  163.                                    ENDIF
  164.                                    ...
  165.                                    ...
  166.                                 
  167.                                 <EOF>
  168.                       
  169.                       Extra statements:
  170.                       
  171.                            ELSE
  172.                            OTHERWISE
  173.                            
  174.                            Example:
  175.                                 
  176.                                 IF upper(STATE) = 'CA'
  177.                                    ...
  178.                                 ELSE
  179.                                    ...
  180.                                 ELSE
  181.                                    ...
  182.                                 ENDIF
  183.                       
  184.  
  185.  
  186.  
  187.  
  188.  
  189.  
  190. User's Guide ____________________________________________________________ Page 3User's Guide ____________________________________________________________ Page 3
  191.  
  192.  
  193. dFIXUP 3.6_________________________________________________________ May 25, 1988dFIXUP 3.6_________________________________________________________ May 25, 1988
  194.  
  195.  
  196.                       If any errors are found during the processing
  197.                       of a  file,  dFIXUP  will  display  the  file
  198.                       statistics, and  then wait  until you press a
  199.                       key.
  200.                                 
  201.             EXAMPLE:  Command line use of dFIXUP:            EXAMPLE:                             
  202.                       
  203.                            DFIXUP PAYROLL.PRG
  204.                            DFIXUP AR*.PRG AP*.PRG
  205.                            DFIXUP @GL.CLP
  206.                            DFIXUP *.PRG
  207.                            
  208.                       Interactive use of dFIXUP:
  209.                            
  210.                            DFIXUP
  211.                                 
  212.             BATCH FILES:            BATCH FILES:
  213.                       dFIXUP will  set the  DOS  ERRORLEVEL  if  it
  214.                       terminates with  an  error  condition.  These
  215.                       errors and the corresponding exit codes are:
  216.             
  217.                       Couldn't open input file                1
  218.                       Couldn't open output file               2
  219.                       Error writing output file               3
  220.                       dFIXUP aborted by user                  6
  221.                       Couldn't install interrupt handler      7
  222.                       Couldn't allocate memory for file list  8
  223.                       Couldn't open .CLP file                 9
  224.             
  225.             
  226.                       dFIXUP will try to diagnose and explain these
  227.                       errors if possible.
  228.             
  229.                       You can  test against these exit code using a
  230.                       IF   ERRORLEVEL   <n>   statement   in   your
  231.                       batchfiles.
  232.             
  233.             SPECS:    dFIXUP  has  the  following  limitations  and            SPECS:                                                 
  234.                       requirements:
  235.             
  236.                       DOS version:             MS/PC-DOS 2.0 or
  237.                                                higher
  238.                       Program file length:     Unlimited
  239.                       Indentation levels:      64 levels
  240.                       Files per run:           256 files
  241.                       File path length:        40 characters
  242.                       Memory requirements:     28KB plus up to 41
  243.                                                bytes for each file
  244.                                                processed.
  245.                       Program line length:     254 characters, as
  246.                                                in dBASE III
  247.                       File size:               17009 bytes
  248.                       File date & time:        5-25-88, 8:00pm
  249.                       
  250.  
  251.  
  252.  
  253. User's Guide ____________________________________________________________ Page 4User's Guide ____________________________________________________________ Page 4
  254.  
  255.  
  256. dFIXUP 3.6_________________________________________________________ May 25, 1988dFIXUP 3.6_________________________________________________________ May 25, 1988
  257.  
  258.  
  259.                       If the file you receive is different in size,
  260.                       or has a different date stamp, do not use the
  261.                       program. It may be a Trojan Horse or infected                                           ____________            
  262.                       with a Virus.                             _____ 
  263.                       
  264.                       dFIXUP was  implemented  using  Microsoft  C3                                                                  _
  265.                       Version 5.0,  using the  standard  C  runtime
  266.                       library.
  267.             
  268.             COMMENTS: dFIXUP 3.6 is exactly the same as dFIXUP 3.5,            COMMENTS:                                              
  269.                       with the  exception that  3.6 has a graphical
  270.                       progress display.
  271.             
  272.                       All comments,  suggestions and contributions,
  273.                       if any,  should be  directed to the program's
  274.                       author:
  275.             
  276.                            Vertical Solutions                           Vertical Solutions
  277.                            Attn: Torsten Hoff                           Attn: Torsten Hoff
  278.                            1925 Century Park East, Suite 1150                           1925 Century Park East, Suite 1150
  279.                            Los Angeles, CA  90067                           Los Angeles, CA  90067
  280.                            
  281.                       The author hereby grants a limited license to
  282.                       copy  and   distribute  dFIXUP  to  all  non-                                                               ____
  283.                       commercial   users    under   the   following                      __________                                   
  284.                       conditions:
  285.             
  286.                            dFIXUP must be distributed in unmodified
  287.                            form,    including    the    README.1ST,
  288.                            DFIXUP.EXE, DFIXUP.TXT,  and  DFIXUP.PRN
  289.                            files.
  290.                            
  291.                            No fee  may be  charged by  anyone for a
  292.                            copy of dFIXUP.
  293.                            
  294.                            dFIXUP may not be distributed as part of
  295.                            any commercial product.
  296.                            
  297.                       The  author  considers  this  product  to  be
  298.                       shareware.   Any    contributions   will   be
  299.                       appreciated.
  300.  
  301.  
  302.  
  303.  
  304.  
  305.  
  306.  
  307.  
  308.  
  309.  
  310.  
  311.             ____________________
  312.             3    Microsoft C is a registered trademark of Microsoft            _                                                      
  313.  
  314.  
  315.  
  316. User's Guide ____________________________________________________________ Page 5User's Guide ____________________________________________________________ Page 5