You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
😎 T-Regx The Dinosaur is really proud to announce its release 0.34.1!
Prepared patterns are a big part of T-Regx library, there actually isn't anything in PHP world (or regular expressions for that matter), that would handle user-data in patterns in such a way as T-Regx's Prepared Patterns with @ placeholders. Among other features, the placeholders are correctly handled with \@ and \Q@\E, as well as comments #comment@\n in Extended Mode (x flag). However, comments are only ended by "\n" when PCRE newline conventions are (*LF). We're sorry to admit, that we didn't take that into account, that when you change line convention to (*CR) (or other convention for that matter), parsing of @ placeholders in comments should be updated accordingly. As of this release, newline conventions are properly being taken into account. We're holding our statement, that @ placeholders aren't being injected into comments.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
😎 T-Regx The Dinosaur is really proud to announce its release
0.34.1
!Prepared patterns are a big part of T-Regx library, there actually isn't anything in PHP world (or regular expressions for that matter), that would handle user-data in patterns in such a way as T-Regx's Prepared Patterns with
@
placeholders. Among other features, the placeholders are correctly handled with\@
and\Q@\E
, as well as comments#comment@\n
in Extended Mode (x
flag). However, comments are only ended by"\n"
when PCRE newline conventions are(*LF)
. We're sorry to admit, that we didn't take that into account, that when you change line convention to(*CR)
(or other convention for that matter), parsing of@
placeholders in comments should be updated accordingly. As of this release, newline conventions are properly being taken into account. We're holding our statement, that@
placeholders aren't being injected into comments.The detailed list of changes is in ChangeLog.md.
Summary of changes:
Prepared patterns now support changing new line conventions with flag
x
(EXTENDED
mode).This code is now valid:
The first placeholder character
"@"
is considered a part of an extended comment, but the secondplaceholder
@
is assigned value'value'
.All types of PCRE newline conventions are supported:
(*LF)
,(*CR)
,(*CRLF)
,(*ANYCRLF)
,(*ANY)
,(*NUL)
.Rawrrrrrrr!
This discussion was created from the release 0.34.1 - New line conventions, PCRE (*VERB).
Beta Was this translation helpful? Give feedback.
All reactions