Changes on BP7SB:


Version 1.01:

- 'Pointer' added to built-in types
- bug fixed: 2.3e-4 will not be changed to 2.3e - 4
- bug fixed: type definition: procedure- and function-types will not break
             the source line
- bug fixed: record definition: case in record definition works now

Version 1.02:

- further bug with procedure- and function-types in headers of functions
  and procedures fixed
- if the option -c:file is not used, BP7SB looks for BP7SB.INI in the
  current directory, if not found then in the directory of BP7SB. The 
  syntax of BP7SB.INI is the same as for the file in the option -c:file
- option -e converts TAB to 8 space characters
- option -u:<f|u|l|n> handles user words (= which do not match neither 
  to built-in nor to own words):
  first occurrence in the source or upper or lower case or no conversion,
  default is mixed case: the first character and the character after '_'
  will be converted to capitals. (in the demo version is -u:<f|u|l|n> 
  option not available, only the default value - mixed case)
- if the source code line has not_closed_brackets, the next line will
  have an extra indent.
- after the characters '.' no space will be inserted
- option -l (not available in the demo version) identifies loops:
  after the keyword 'END' the loop_identifier will be inserted, if you 
  don't have there any remarks beginning with '{' or '('. The labels are:
  { with }, { while }, { if }, { if else }, { for }, { case }, 
  { case else }, { case label }, { record }, { object }, { asm }, { ? }
  The 'END's of Program, Unit, Procedure, Function, Constructor, Destructor
  and the unrecognized loops are marked with { ? }.
- the help screen is divided into 2 pages. (q - quit, other - 2nd page 
  and exit)

Version 1.03

- the loop_identifiers have the same case than the reserved words
- the keyword will not be divided into 'subtokens': e.g. Bar3D is ONE token
- mixed case for user words: the first character and the character after
  '_' and ['0'..'9'] will be converted to capitals
- all features are available in the unregistered version IF THE SOURCE
  HAS NOT MORE THAN 100 LINES
- option -i:<e|n> controls how to 'extra indent' the next lines after
  not_closed_brackets: one extra indent for each not_closed_bracket or
  do not extra indent. Default is one extra indent for all 
  not_closed_brackets. (i.e. the next lines get only one extra indent
  even if the source line has more than one not_closed_bracket)
- option -n:<u|l> handles TVision keywords
- after the keyword ``inline'' no space will be inserted (up to ``;'')

Version 1.04

- breaking lines (-s:m) works now (hopefully :-) also for strings
- in order to make the executable more compact, the handling of
  built-in keywords was completely rewritten
- THE UNREGISTERED VERSION HANDLES NOW FILES UP TO 300 LINES
