ianh/owl

Issues

• How would you handle optional trailing semicolons?

  #4 opened 4 months ago by mqudsi
  3

• Option to switch priority between user-defined tokens and built-in tokens

  #3 opened 6 years ago by mqudsi
  4

• hex integer

  #30 opened 4 months ago by ozbolt-abrantix
  3

• Is the disjointness requirement for call and exit symbols really necessary?

  #44 opened a year ago by modulovalue
  4

• Confusing start symbol and missing ambiguity warning.

  #42 opened a year ago by modulovalue
  5

• Identical "bracket" symbols not supported?

  #43 opened a year ago by modulovalue
  6

• Example: Dart lexer.

  #38 opened a year ago by modulovalue
  1

• non-breaking space is not a right turnstile

  #41 opened a year ago by modulovalue
  4

• token ' ' can't be used as both a whitespace and a normal keyword

  #40 opened a year ago by modulovalue
  3

• Storing grammars in the url.

  #39 opened a year ago by modulovalue
  0

• Incremental parsing of visibly pushdown languages?

  #36 opened a year ago by modulovalue
  3

• Deforested tree construction possible?

  #37 opened a year ago by modulovalue
  2

• Feature request: Unicode properties

  #35 opened a year ago by data-man
  1

• Compiler warning in generated code

  #34 opened a year ago by WarrenWeckesser
  2

• Out-of-bounds Read Vulnerability

  #33 opened a year ago by circeanubogdan
  1

• Shadowing of local variable

  #29 opened 2 years ago by ozbolt-abrantix
  1

• Hexadecimal input is parsed as number instead of integer

  #28 opened 3 years ago by falkoschindler
  3

• Can't include parser.h in C++ project due to "class" keyword

  #27 opened 3 years ago by falkoschindler
  2

• Potential crash after calloc due to empty node->slots

  #26 opened 3 years ago by falkoschindler
  1

• Build errors and warnings

  #25 opened 3 years ago by WarrenWeckesser
  4

• ER: Regex-defined custom tokens

  #20 opened 4 years ago by numist
  2

• Parser doesn't compile with multiple custom tokens

  #21 opened 4 years ago by numist
  4

• Provide a way to include two different parsers without symbol conflicts

  #19 opened 5 years ago by ianh
  4

• How would one handle a macro/define keyword, is it possible currently?

  #18 opened 5 years ago by warvstar
  3

• Addition of a build system generator

  #17 opened 5 years ago by elfring
  2

• Completion of error handling

  #16 opened 5 years ago by elfring
  6

• reserved identifier violation

  #15 opened 5 years ago by elfring
  4

• Indentation sensitive parsing.

  #12 opened 5 years ago
  12

• Unexpected result when getting string or identifier

  #13 opened 5 years ago
  4

• syntactic sugar for 'separated by'

  #9 opened 6 years ago by modernserf
  8

• 'integer' token type?

  #7 opened 6 years ago by ianh
  1

• Documentation on Custom Tokenization

  #11 opened 6 years ago by TheThirdOne
  8

• Unable to install (make)

  #10 opened 6 years ago by enjoysmath
  9

• Reserved words for field names

  #6 opened 6 years ago by ianh
  2

• Other types of numbers?

  #2 opened 6 years ago by WarrenWeckesser
  5