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

Fix double-escaped {CCOMMENT} rule pattern #33

Merged
merged 1 commit into from
Nov 11, 2016
Merged

Conversation

jparise
Copy link
Collaborator

@jparise jparise commented Nov 11, 2016

This pattern's literal \ characters were unnecessarily escaped,
probably as a transcription error from the original lex source code.
This causes this pattern to misbehave and conflict with the {COMMENT}
rule.

The test suite has been extended to cover juxtapositional comment cases,
too, which ensures were correctly account for whitespace within and
around comments.

This pattern's literal `\` characters were unnecessarily escaped,
probably as a transcription error from the original lex source code.
This causes this pattern to misbehave and conflict with the {COMMENT}
rule.

The test suite has been extended to cover juxtapositional comment cases,
too, which ensures were correctly account for whitespace within and
around comments.
@coveralls
Copy link

coveralls commented Nov 11, 2016

Coverage Status

Coverage remained the same at 99.296% when pulling 3b19b6d on lexer-comments into 2eddb4e on master.

@jparise jparise merged commit b7dc23e into master Nov 11, 2016
@jparise jparise deleted the lexer-comments branch November 11, 2016 00:20
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

Successfully merging this pull request may close these issues.

3 participants