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

Add utf8::bom and utf16::bom helper rules. #65

Merged
merged 1 commit into from
Jul 19, 2017

Conversation

samhocevar
Copy link
Contributor

I find myself reimplementing a rule for the optional byte-order mark in every UTF-8 parser I write. The character is automatically added by many Windows-based text editors, so it makes sense to have it in pegtl::utf8 and pegtl::utf16.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 99.904% when pulling 6eb4d7c on lolengine:feature-unicode-bom into b47152c on taocpp:master.

@d-frey d-frey merged commit 51b1d4e into taocpp:master Jul 19, 2017
@d-frey
Copy link
Member

d-frey commented Jul 19, 2017

Thanks, bom seems to be sufficiently general and is a welcomed addition. I also added a bom rule for UTF-32 to detect them, plus some cleanups.

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

Successfully merging this pull request may close these issues.

3 participants