Skip to content
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

BNFC backend ignoring token definitions #73

Open
dkasak opened this issue Nov 20, 2017 · 1 comment
Open

BNFC backend ignoring token definitions #73

dkasak opened this issue Nov 20, 2017 · 1 comment

Comments

@dkasak
Copy link

dkasak commented Nov 20, 2017

The BNFC backend is (predictably) ignoring any BNFC token definition since they only get encoded into the Alex source file and QuickFuzz just ends up using the Arbitrary instance of String.

For instance, given the following BNFC grammar:

Program. Exp ::= CIdent ;

token CIdent (lower (lower | digit | '_')*) ;

Produces the following non-printable gibberish:

�(�2

Is it possible to be smarter about this?

@gaa-cifasis
Copy link
Member

For some reason, I did not receive an email with this issue in my inbox. Sorry for the delay to answer!

I think we should ask @ebadi, the user that contributed adding the BNFC backend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants