
Anomaly Report:  Regen 1.0

---[1]--------------------------------------------------------------------

PROBLEM:  Regen doesn't recognize the obsolete directives << set alias >>
or << set dialect to >>, which were used in the Genifer 2.0 templates.

COMMENT:  This problem was fixed in version 1.02.

--------------------------------------------------------------------------


Anomaly Report:  Regen 1.0

---[2]--------------------------------------------------------------------

PROBLEM:  During code generation, Regen crashes with the ambiguous message
"Internal error 5333".

COMMENT:  The error is caused by corruption of the Genifer index files.
That corruption, in turn, is apparently caused by a fault in the Clipper
libraries (the Clipper 5.01 compiler was used to create Regen), making it
beyond Bytel's immediate control.

WORKAROUND:  Delete the Genifer index files using the command

                   C:\GENIFER\MYPROJECT>DEL GEN*.NTX

Then REGEN your program again.  The index files will be automatically
rebuilt, and the program should generate without error.

--------------------------------------------------------------------------


Anomaly Report:  Regen 1.0

---[3]--------------------------------------------------------------------

PROBLEM:  The genvars [field #size] and [field #width] are sometimes
generated inaccurately by REGEN.

COMMENT:  [Field #size] is not used in the standard Bytel templates, and
[field #width] is used only sparingly, so this problem will probably
affect only users who've created custom templates.

WORKAROUND:  These two genvars are evaluated properly by Genifer, so any
program modules where they are critical may be generated using the
old-fashioned, one-file-at-a-time method.  REGEN can still be useful for
fast generation of interim versions until this bug is fixed.

--------------------------------------------------------------------------


Anomaly Report:  Regen 1.0

---[4]--------------------------------------------------------------------

PROBLEM:  If you include spaces in an index expression (for example,
"CR_DATE + BOAT" instead of "CR_DATE+BOAT"), the index expression does
not generate correctly.

WORKAROUND:  Don't leave blank spaces within your index expressions.
(Remarkable, Holmes!  I never would have thought of that!)

--------------------------------------------------------------------------

