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 support for ES6 Unicode #17

Open
CJex opened this issue Dec 14, 2014 · 4 comments
Open

Add support for ES6 Unicode #17

CJex opened this issue Dec 14, 2014 · 4 comments
Assignees
Milestone

Comments

@CJex
Copy link
Owner

CJex commented Dec 14, 2014

Support /\u{12345}/u .

@CJex CJex self-assigned this Dec 14, 2014
@CJex CJex added this to the ES6 milestone Dec 14, 2014
@pouyakary
Copy link

pouyakary commented Dec 1, 2016

before I start

@JexCheng hi!
First of all we owe you a super big thanks. We're making a visual language that compiles to RegEx in order to make it more clean to write complex regexp. And we had to write a reverse compiler to compile back regexp into my language. In that project we extensively used Regulex's parser. (we also have a TypeScript deceleration file for regulex that I'm working on and will soon contribute it back to you). So we wanted to say thank for you awesome parser. We tried many projects and none of them had an AST better than yours, without your parser we had to go so much more far to have it.

\p{ .. } / \P{ ... } are not supported in Regulex

As in RegExp Unicode Property Escapes by TC39 there are now some more Unicode sets that you can add with \p{ .. } and exclude with \P{ ... }:

/\p{Decimal_Number}/u

There are some good documentations here. As we are now heavily dependent on Regulex's parser we want to invest on it. If you like we like to contribute back. So we like to handle this. Just we would love to know how you like the AST structure for this new elements to be.

@CJex
Copy link
Owner Author

CJex commented Dec 2, 2016

@pmkary This project will be fully rewrited in another compile to js X language(but keep AST compatible), so currently these features would not be made in this version.

@pouyakary
Copy link

Thank you. So I think we have to fork the project. Looking forward towards your new compiler.

@PeterlitsZo
Copy link

How about now 👀

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

3 participants