Content deleted Content added
Announcement (talk | contribs) |
minor fmt tweaks, remove malformed empty section |
||
Line 1:
{{WikiProject Computing|class=|importance=|software=yes|software-importance=}}
== python regex module missing ==
https://pypi.python.org/pypi/regex supports a broader set of features than pythons standard re module, especially recursive pattern matching --[[User:ThomasKalka|ThomasKalka]] ([[User talk:ThomasKalka|talk]]) 11:02, 28 March 2016 (UTC)
== Jan-2010 Update ==
* removing notes that something has only been available since '2007' (version was mentioned, but released 5 years ago)....
* remove notes on Unicode support where the note was (supports ALL, including binary )... if it supports it, it supports it, a special note should not be required for 'all', rather, only 'partial' support cases should be noted.
Line 18 ⟶ 15:
* Note 2: (not mentioned in the article) -- PCRE gets it's code from Perl -- so it's features generally track Perl's. PCRE is an acronym for Perl Compatible Regular Expression. and the engine in ruby derives from PCRE -- and tries to track it's features. The Ruby engine was done, specifically to add Japanese support BEFORE UTF-8 started becoming prevalent. Thus it supported 16-bits early on, but for locale-based charsets for Japanese. It wasn't really until it added UTF-8 support that it got full Unicode support.
<small> (This is written after updating ""Part 2"" . I'm looking at ""Part 3"" to see what is salvageable there... started to writeup comments, but better I do it and then say what was done, as if I get hung up on saying what I'll do, I may not get it done...(am getting a bit tired of this update stuff already)... </small> [[User:Athenae|Astara Athenea]] ([[User talk:Athenae|talk]]) 21:44, 22 January 2012 (UTC)
== Ill-defined terms ==
Line 50 ⟶ 46:
: I've gone ahead and done this. --[[User:Monger|Monger]] 01:00, 20 July 2007 (UTC)
== Unicode property support ==
Line 101 ⟶ 96:
In new implementations, as seen in a [https://github.com/tc39/proposal-regexp-named-groups proposal for named capture groups] has been added.
<ref>{{Cite web|url=https://codereview.chromium.org/2050343002|title=Issue 2050343002: [regexp] Experimental support for regexp named captures - Code Review|website=codereview.chromium.org|access-date=2018-02-02}}</ref>
ES2018 has a [https://github.com/tc39/proposal-regexp-lookbehind proposal for lookbehind], which was already implemented in some engines.<ref>{{Cite web|url=https://v8project.blogspot.com/2016/02/regexp-lookbehind-assertions.html|title=V8 JavaScript Engine: RegExp lookbehind assertions|last=Hablich|first=Michael|date=2016-02-26|website=V8 JavaScript Engine|access-date=2018-02-02}}</ref>
| |||