# JLex Bugs

The following bugs reports are provided to inform users of known problems with Java-Lex. These reports are in the form of email messages describing the problem encountered.

If you have an additional bug report, describing a problem not listed in one of these reports, please mail it to cananian@alumni.princeton.edu.

Please check your JVM before mailing in a bug report! There have been a spate of recent reports which have been traced down to buggy virtual machines (e.g. `kaffe`) or compilers (e.g. `pizza`). Please take a second to check that your bug can be reproduced using "standard" tools before reporting a bug.

- Bug 1: Incorrect parsing of valid regular expression with complicated macro expansion.
  Fixed 7/25/99 in version 1.2.4. Reported 7/26/96.
- Bug 2: Cross platform use of Java-Lex and newline characters.
  Fixed 11/1/96 in version 1.1.2. Reported 8/11/96.
- Bug 3: Compiler error relating to public class.
  Fixed 9/12/96 in version 1.1.1. Reported 9/3/96.
- Bug 4: Inconsistent macro expansion.
  Fixed 11/1/96 in version 1.1.2. Reported 9/4/96.
- Bug 5: Start of line symbol (^).
  Fixed in version 1.2.5. Reported 9/10/96.
- Bug 6: Character codes greater than 127.
  Fixed 9/15/97 in version 1.2.1. Reported 9/11/96.
- Bug 7: Bad error messages on macro error.
  Fixed 11/1/96 in version 1.1.2. Reported 10/24/96.
- Bug 8: Accept buffer does not dynamically increase in size.
  Fixed 11/1/96 in version 1.1.2. Reported 10/30/96.
- Bug 9: Space character not parsed properly.
  Fixed 7/24/99 in version 1.2.4. Reported 7/29/97.
- Bug 10: Use of deprecated String constructor.
  Fixed 9/15/97 in version 1.2.1. Reported 4/28/97.
- Bug 11: Some machines can't effectively use a command line.
  Supplementary classes included here. Reported 2/24/97.
- Bug 12: Non-portable line separator string.
  Fixed in version 1.2.5. Reported 9/10/97.
- Bug 13: Yylex.class includes methods longer than 65K.
  Fixed 6/26/98 in version 1.2.3. Reported 6/18/98.
- Bug 14: More problems with character codes greater than 127.
  Fixed 7/25/99 in version 1.2.5. Reported 11/12/97.