Skip to content

Unexpected exception encountered. Not normalised type = CHAR #939

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
AidanSmiley opened this issue Oct 5, 2021 · 1 comment · Fixed by #996
Closed

Unexpected exception encountered. Not normalised type = CHAR #939

AidanSmiley opened this issue Oct 5, 2021 · 1 comment · Fixed by #996
Labels
bug Not working as intended
Milestone

Comments

@AidanSmiley
Copy link

Hello.
I'm in the process of making a scanner for my Compiler Design class using JFlex and Cup and ran into this error. Not 100% sure if it's from my own code or something else and figured I'd report the bug anyway. Attached is the output after attempting to compile as well as a link to a repo of my current project that should reproduce the bug.

Any help at all would be appreciated thank you.

https://github.com/AidanSmiley/CompilerProjectP1/tree/main

image

@lsf37 lsf37 added the bug Not working as intended label Oct 5, 2021
@lsf37
Copy link
Member

lsf37 commented Oct 5, 2021

This does look like an actual jflex bug. Thanks for reporting it, I'll take a closer look in the next few days.

@lsf37 lsf37 added this to the 1.9.0 milestone Nov 19, 2021
lsf37 added a commit that referenced this issue Jan 1, 2023
Because we allow macros in the syntax for char class contents, we can
get arbitrary regular expressions inside, not just char class content
expressions.

This commit turns the previous "cannot happen" check for such a case
into proper error reporting.

Fixes #888 and #939
@lsf37 lsf37 linked a pull request Jan 1, 2023 that will close this issue
2 tasks
lsf37 added a commit that referenced this issue Jan 1, 2023
Because we allow macros in the syntax for char class contents, we can
get arbitrary regular expressions inside, not just char class content
expressions.

This commit turns the previous "cannot happen" check for such a case
into proper error reporting.

Fixes #888 and #939
lsf37 added a commit that referenced this issue Jan 1, 2023
Because we allow macros in the syntax for char class contents, we can
get arbitrary regular expressions inside, not just char class content
expressions.

This commit turns the previous "cannot happen" check for such a case
into proper error reporting.

Fixes #888 and #939
lsf37 added a commit that referenced this issue Jan 1, 2023
lsf37 added a commit that referenced this issue Jan 1, 2023
Because we allow macros in the syntax for char class contents, we can
get arbitrary regular expressions inside, not just char class content
expressions.

This commit turns the previous "cannot happen" check for such a case
into proper error reporting.

Fixes #888 and #939
lsf37 added a commit that referenced this issue Jan 1, 2023
Signed-off-by: Gerwin Klein <lsf@jflex.de>
lsf37 added a commit that referenced this issue Jan 1, 2023
Because we allow macros in the syntax for char class contents, we can
get arbitrary regular expressions inside, not just char class content
expressions.

This commit turns the previous "cannot happen" check for such a case
into proper error reporting.

Fixes #888 and #939

Signed-off-by: Gerwin Klein <lsf@jflex.de>
lsf37 added a commit that referenced this issue Jan 1, 2023
lsf37 added a commit that referenced this issue Jan 1, 2023
Because we allow macros in the syntax for char class contents, we can
get arbitrary regular expressions inside, not just char class content
expressions.

This commit turns the previous "cannot happen" check for such a case
into proper error reporting.

Fixes #888 and #939
lsf37 added a commit that referenced this issue Jan 1, 2023
lsf37 added a commit that referenced this issue Jan 1, 2023
Because we allow macros in the syntax for char class contents, we can
get arbitrary regular expressions inside, not just char class content
expressions.

This commit turns the previous "cannot happen" check for such a case
into proper error reporting.

Fixes #888 and #939
@lsf37 lsf37 closed this as completed in #996 Jan 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Not working as intended
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants