On the left are pomsky expressions, on the right is the compiled regex:
```py
'hello world' # hello world
'hello'{1,5} # (?:hello){1,5} 'hello'* # (?:hello)* 'hello'+ # (?:hello)+
'hello'{1,5} lazy # (?:hello){1,5}? 'hello'* lazy # (?:hello)*? 'hello'+ lazy # (?:hello)+?
'hello' | 'world' # hello|world
['aeiou'] # [aeiou] ['p'-'s'] # [p-s]
[word] [space] [n] # \w\s\n
[w 'a' 't'-'z' U+15] # [\wat-z\x15]
!['a' 't'-'z'] # [^at-z]
[Greek] U+30F Grapheme # \p{Greek}\u030F\X
Start End # ^$ % 'hello' !% # \bhello\B
'terri' ('fic' | 'ble') # terri(?:fic|ble)
:('test') # (test)
:name('test') # (?P
'foo' | 'bar' # (?=foo|bar) << 'foo' | 'bar' # (?<=foo|bar) !>> 'foo' | 'bar' # (?!foo|bar) !<< 'foo' | 'bar' # (?
:('test') ::1 # (test)\1
:name('test') ::name # (?P
range '0'-'999' # 0|[1-9][0-9]{0,2} range '0'-'255' # 0|1[0-9]{0,2}|2(?:[0-4][0-9]?|5[0-5]?|[6-9])?|[3-9][0-9]? ```
```rust let operator = '+' | '-' | '*' | '/'; let number = '-'? [digit]+;
number (operator number)* ```
Read the book to get started, or check out the CLI program, the Rust library and the procedural macro.
Normal regexes are very concise, but when they get longer, they get increasingly difficult to
understand. By default, they don't have comments, and whitespace is significant. Then there's the
plethora of sigils and backslash escapes that follow no discernible system:
(?<=) (?P<>) .?? \N \p{} \k<> \g''
and so on. And with various inconsistencies between regex
implementations, it's the perfect recipe for confusion.
Pomsky solves these problems with a new, simpler but also more powerful syntax:
Pomsky is currently compatible with PCRE, JavaScript, Java, .NET, Python, Ruby and Rust. The regex flavor must be specified during compilation, so pomsky can ensure that the produced regex works as desired on the targeted regex engine.
Note: You should enable Unicode support in your regex engine, if it isn't enabled by default. This is explained here.
Never compile or execute an untrusted Pomsky expression on your critical infrastructure. This may make you vulnerable for denial of service attacks, like the Billion Laughs attack.
Pomsky looks for mistakes and displays helpful diagnostics:
I wrote an in-depth comparison with similar projects, which you can find here.
You can find the Roadmap here.
You can contribute by using Pomsky and providing feedback. If you find a bug or have a question, please create an issue.
I also gladly accept code contributions. To make sure that CI succeeds, please run cargo fmt
,
cargo clippy
and cargo test
before creating a pull request.
Dual-licensed under the MIT license or the Apache 2.0 license.