Skip to content

Releases: tom-lord/regexp-examples

Backspaces implemented

17 Jan 20:04
Compare
Choose a tag to compare

For example, /[\b]/.examples now works!

Also did some tidy up in the documentation and gemsec (e.g. the gem date now works properly)

Exceptions thrown for "bad" input

17 Jan 19:14
Compare
Choose a tag to compare

"Illegal" input, such as word anchors (/\bWORD\b/.examples), will raise an IllegalSyntax error. These features will never be suported by the gem.

"Unsupported" input, such as POSIX bracket expressions (/[[:space:]]/.examples), will raise an UnsupportedSyntax error (as opposed to just giving "examples" that do not match!!). These features may, one day, be supported by the gem.

Unicode and escape sequence support

17 Jan 16:44
Compare
Choose a tag to compare

The gem can now handle input such as:

/\x74\x68\x69\x73/.examples #=> ["this"]
/\u6829/.examples #=> ["栩"]

Control character support

16 Jan 17:40
Compare
Choose a tag to compare

Added support for control characters, e.g. /\cA/.examples

Also a couple of obscure bug fixes.

Illegal Syntax exceptions

15 Jan 10:21
Compare
Choose a tag to compare

If you try to use "illegal" syntax, like /(?=lookahead)/.examples, the gem will now raise an exception.
This is not yet implemented for unsupported syntax like /\p{Arabic}/.examples; this will be added in the next release.

There is also a MAJOR re-write of how capture groups and backreferences are managed in the backend. This was mainly just a code clean-up, although it does provide some user benefits which I have yet to document.

Escaped characters bug fix

14 Jan 17:49
Compare
Choose a tag to compare

Previous versions did not work properly for:

/\S/, /\D/, /\W/

These now work, as well as the newly added /\h/ and /\H/

v0.2.0: More detail on supported groups

13 Jan 21:46
Compare
Choose a tag to compare

Capture groups are now bug-free (I think) and fully supported!

v0.1.0

12 Jan 09:33
Compare
Choose a tag to compare

Non- and named-capture groups now supported.

There are still some (relatively) obscure bugs to fix, but for the most part this is now working!