#pcre — Public Fediverse posts

Атомарные регулярные выражения

Регулярные выражение обладают возможностями отслеживания пройденного пути и рефлексией. Разберемся, как использовать эти возможности для захвата фрагментов текста, как применить к ним цвет и вывести в консоль.

https://habr.com/ru/articles/1057658/

#regex #регулярки #регулярные_выражения #парсинг #pcre #алгоритмы #изучение_программирования #autohotkey #регулярное_выражение #regular_expressions

Did you know #Microslop #Excel supports #PCRE?

I was trying to extract some strings from a cell (written by one of those people who think that Excel is is just "Word with lines") when I thought "ugh, I wish I could just use a #regex."

Then I noticed this. Unfortunately, the documentation doesn't explain much, so it took some time to figure out their weirdness; no delimiters, no modifiers, etc. That aside, it does support capture groups, so I was able to extract all the values with a single regex.

Pretty handy!

Oha, #inotifywait kann keine #PCRE (Negatives Lookahead). Wie kann man dann mit -exclude sinnvoll Dateiendungen ausschließen?

Muss ich jetzt erst einen Converter entwickeln, um die Kernkonstrukte und Negationen auf POSIX abzubilden??

inotifywait patchen könnte einfacher sein 🤔

Oha, #inotifywait kann keine #PCRE (Negatives Lookahead). Wie kann man dann mit -exclude sinnvoll Dateiendungen ausschließen?

Muss ich jetzt erst einen Converter entwickeln, um die Kernkonstrukte und Negationen auf POSIX abzubilden??

inotifywait patchen könnte einfacher sein 🤔

@dm

Always. I kinda wish #PCRE (Perl-Compatible Regular Expressions) were more accepted, because some of those shortcuts (particularly \s) are very space-saving compared to their traditional counterparts ([[:space:]]), but since only GNU grep provides a PCRE option (-P), I avoid using it for the sake of greater compatibility.

@dm

Always. I kinda wish #PCRE (Perl-Compatible Regular Expressions) were more accepted, because some of those shortcuts (particularly \s) are very space-saving compared to their traditional counterparts ([[:space:]]), but since only GNU grep provides a PCRE option (-P), I avoid using it for the sake of greater compatibility.

@christmastree

Nice! Good old #PCRE.

FYI, Mastodon doesn't support markdown formatting or longer posts, but Hometown, GlitchSocial (both forks of Mastodon) and GoToSocial and snac (both independent fediverse server implementations) do. :)

@christmastree

Nice! Good old #PCRE.

FYI, Mastodon doesn't support markdown formatting or longer posts, but Hometown, GlitchSocial (both forks of Mastodon) and GoToSocial and snac (both independent fediverse server implementations) do. :)

From #punchcards to powerful #code in #opensource projects #PCRE and #Exim, Philip Hazel’s career is an exciting journey of #FOSS success and the evolution of #tech! 🐧

Dive into Hazel’s story on @LWN and consider carrying on the torch maintaining #PCRE2:

https://t.ly/RLY3Q

#LPI #LWN #techhistory #freesoftware #softwaredevelopment #github #perl #Linux #Unix #GPL #Apache #MariaDB

From #punchcards to powerful #code in #opensource projects #PCRE and #Exim, Philip Hazel’s career is an exciting journey of #FOSS success and the evolution of #tech! 🐧

Dive into Hazel’s story on @LWN and consider carrying on the torch maintaining #PCRE2:

https://t.ly/RLY3Q

#LPI #LWN #techhistory #freesoftware #softwaredevelopment #github #perl #Linux #Unix #GPL #Apache #MariaDB

How free software hijacked Philip Hazel's life [LWN.net]

Link

@AnarchoDoggo @silberfuchs @swaggboi #Perl did not “give” the world #PCRE; Philip Hazel wrote it for the #Exim mail transport agent software in 1997.

I like to refer to it as “*Partially* Compatible Regular Expressions.” Here is the project’s documentation on (some) areas where it will disappoint you: https://PCRE.org/current/doc/html/pcre2compat.html

#PCRE4J 0.3.0 has been released (#Java / #PCRE2 / #PCRE / #PerlCompatibleRegularExpressions / #Perl / #RegularExpression) https://pcre4j.org/

#PCRE4J 0.3.0 has been released (#Java / #PCRE2 / #PCRE / #PerlCompatibleRegularExpressions / #Perl / #RegularExpression) https://pcre4j.org/

#PCRE2 10.44 has been released (#PCRE / #PerlCompatibleRegularExpressions / #Perl / #RegularExpression) https://pcre.org/

#PCRE2 10.44 has been released (#PCRE / #PerlCompatibleRegularExpressions / #Perl / #RegularExpression) https://pcre.org/

@n1vux @driusan @ai6yr Or as I like to say: #PCRE isn’t PC

@perl #Perl

@neustradamus #PCRE continues to be a misnomer; it’s a modified subset of #Perl #RegularExpressions with dozens of differences: https://pcre.org/current/doc/html/pcre2compat.html

It's not "(C)ompatible." Accept no substitutes: https://perldoc.perl.org/perlre

#PCRE2 #PerlIncompatibleRegularExpressions #RegularExpression #RegExes #RegExps #regex #regexp

#PCRE2 10.43 has been released (#PCRE / #PerlCompatibleRegularExpressions / #Perl / #RegularExpression) https://pcre.org/

#PCRE2 10.43 has been released (#PCRE / #PerlCompatibleRegularExpressions / #Perl / #RegularExpression) https://pcre.org/

#BSI WID-SEC-2023-1983: [UPDATE] [mittel] #PCRE (#Perl #Compatible #Regular #Expressions): Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in PCRE (Perl Compatible Regular Expressions) ausnutzen, um einen Denial of Service Angriff durchzuführen.

https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2023-1983

#BSI WID-SEC-2023-1983: [UPDATE] [mittel] #PCRE (#Perl #Compatible #Regular #Expressions): Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in PCRE (Perl Compatible Regular Expressions) ausnutzen, um einen Denial of Service Angriff durchzuführen.

https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2023-1983

@randomgeek @gizmomathboy @pdcawley The name #PCRE bugs me to no end, because it isn’t

Has anyone ever made GNU COBOL talk to PCRE, or any other regex library? I feel like I'm close to getting it to work with PCRE, but i'm trying to piece together multiple sets of docs, and I’m still feeling a bit lost. I keep saying, “Hmm. I'm surprised that worked" with each step forward. 🤣

#COBOL #GNU #regex #pcre

Has anyone ever made GNU COBOL talk to PCRE, or any other regex library? I feel like I'm close to getting it to work with PCRE, but i'm trying to piece together multiple sets of docs, and I’m still feeling a bit lost. I keep saying, “Hmm. I'm surprised that worked" with each step forward. 🤣

#COBOL #GNU #regex #pcre

@mjgardner
Searching #PCRE you came up as the first result.

@mjgardner
Searching #PCRE you came up as the first result.

#regex #question

I was going through some HTML markup/ content where my <h1>,<hx> tags have no anchors/ ID's. pain in the butt to do that manually if i want anchors, It occurred to me: why don't I just process the markup and use the &#x003C;h1&#x003e; (..contents ...) &#x003C;/h1&#x003e;
but the (...contents...) atom needs filtering. E.g. "this just in", maybe I want "this_just_in"

That's not really possible w/ #PCRE is it?

Maybe this is something #sed can do? Im not super fmlr w/ all gnutils

#regex #question

I was going through some HTML markup/ content where my <h1>,<hx> tags have no anchors/ ID's. pain in the butt to do that manually if i want anchors, It occurred to me: why don't I just process the markup and use the &#x003C;h1&#x003e; (..contents ...) &#x003C;/h1&#x003e;
but the (...contents...) atom needs filtering. E.g. "this just in", maybe I want "this_just_in"

That's not really possible w/ #PCRE is it?

Maybe this is something #sed can do? Im not super fmlr w/ all gnutils

@jernej__s @malwareminigun / \p{Quotation_Mark} solved \p{Quotation_Mark} /x #Perl #regex

(Note that doesn’t work with software using the #PCRE Perl “Compatible” #RegularExpression library because its #Unicode support is worse: https://www.pcre.org/current/doc/html/pcre2unicode.html#:~:text=Only%20the%20short%20names%20for%20properties%20are%20supported)

@jernej__s @malwareminigun / \p{Quotation_Mark} solved \p{Quotation_Mark} /x #Perl #regex

(Note that doesn’t work with software using the #PCRE Perl “Compatible” #RegularExpression library because its #Unicode support is worse: https://www.pcre.org/current/doc/html/pcre2unicode.html#:~:text=Only%20the%20short%20names%20for%20properties%20are%20supported)

@barubary @Edent Or #PCRE, the Perl Compatible* Regular Expression engine, Which is used by #PHP and #Rlang as well as the #Apache and #nginx HTTP servers, #nmap, #Postfix, and #Exim (for which it was originally written).

You can even make your #Perl compatible with PCRE instead of other Perl, but you should have a good reason (performance mostly): https://metacpan.org/pod/re::engine::PCRE2

* PCRE2’s own documentation highlights nineteen separate significant differences: https://www.pcre.org/current/doc/html/pcre2compat.html

@barubary @Edent Or #PCRE, the Perl Compatible* Regular Expression engine, Which is used by #PHP and #Rlang as well as the #Apache and #nginx HTTP servers, #nmap, #Postfix, and #Exim (for which it was originally written).

You can even make your #Perl compatible with PCRE instead of other Perl, but you should have a good reason (performance mostly): https://metacpan.org/pod/re::engine::PCRE2

* PCRE2’s own documentation highlights nineteen separate significant differences: https://www.pcre.org/current/doc/html/pcre2compat.html

@Codely @drupler It helps to build your complicated #RegularExpressions in pieces and store them in separate variables. You can then test them in isolation and not be confused when you concatenate them together for your actual matching.

Both #PHP and #JavaScript also support named capture groups if you’re doing replacements. They’re a lot more readable.

Also, PHP’s #PCRE-based engine has a PCRE_EXTENDED flag that lets you add whitespace, newlines, and comments.

#regexes #regexps

@Codely @drupler It helps to build your complicated #RegularExpressions in pieces and store them in separate variables. You can then test them in isolation and not be confused when you concatenate them together for your actual matching.

Both #PHP and #JavaScript also support named capture groups if you’re doing replacements. They’re a lot more readable.

Also, PHP’s #PCRE-based engine has a PCRE_EXTENDED flag that lets you add whitespace, newlines, and comments.

#regexes #regexps

@thfr

Good to know I don't have to fetch GNU ls ^___^

But honestly, not missing it. :D

Is colorls developed by one of the #OpenBSD devs, or is it imported from #FreeBSD?

The only thing I sometimes miss is the #PCRE. Even vim seems to be missing it, for some reason.
Oh, and emoji. Emojis work great in Chromium, but almost nowhere else.

@thfr

Good to know I don't have to fetch GNU ls ^___^

But honestly, not missing it. :D

Is colorls developed by one of the #OpenBSD devs, or is it imported from #FreeBSD?

The only thing I sometimes miss is the #PCRE. Even vim seems to be missing it, for some reason.
Oh, and emoji. Emojis work great in Chromium, but almost nowhere else.

I just completed "Tuning Trouble" - Day 6 - Advent of Code 2022 #AdventOfCode in #regex (#pcre #grep) https://github.com/lucaswiman/advent-of-code/blob/main/2022/0006/solve.regex
https://adventofcode.com/2022/day/6

Uses negative lookahead assertions and backreferences to force uniqueness. Then feed it to `grep - Pbo` (P=Perl regexes, b=byte offset, o=only match) to get the position.

@RL_Dane @benjaminhollon @marcxjo #PCRE was “inspired by” #Perl #RegularExpressions. It was developed as a replacement for the original Spencer #regexp library used by the #Exim mail transfer agent. Although there has been some cross-pollination of features, they’re independent projects with different goals.

#PCRE2 documents some of its differences with Perl here: https://www.pcre.org/current/doc/html/pcre2compat.html

@RL_Dane @benjaminhollon @marcxjo #PCRE was “inspired by” #Perl #RegularExpressions. It was developed as a replacement for the original Spencer #regexp library used by the #Exim mail transfer agent. Although there has been some cross-pollination of features, they’re independent projects with different goals.

#PCRE2 documents some of its differences with Perl here: https://www.pcre.org/current/doc/html/pcre2compat.html

@mjgardner @benjaminhollon @marcxjo

I wonder where #PCRE came from, if not from Perl, then?

@mjgardner @benjaminhollon @marcxjo

I wonder where #PCRE came from, if not from Perl, then?

@RL_Dane
#PCRE… isn’t. One of these days I’m going to have to catalog the differences between it and the firepower of a fully armed and operational #Perl #regexp battlestation https://perldoc.perl.org/perlre

@benjaminhollon @marcxjo

@benjaminhollon @TheTuzu

I use bc, but python is good, too.

I'm tempted to use perl as grep on #OpenBSD for access to yummy #PCRE ^__^

@benjaminhollon @marcxjo

Regex is really quite decent, but definitely an acquired taste.

I particularly like #regex in #perl, because #PCRE (Perl-Compatible Regular Expressions) are super powerful, mostly instead of needing to use large character classes like [[:alnum:]], [[:space:]] and [0-9], you can just write \w, \s, and \d, respectively. There's also the massively powerful \b, which represents a word border.

...

#Programming #languages I used professionally, or for real/finished personal projects:

- #Bash
- #CSharp
- #CoffeeScript (ugh)
- #Haskell
- #Java
- #JavaScript
- #Kotlin
- #Perl
- #PHP
- #Python
- #Ruby
- #Scala
- #TypeScript

DSLs that matter:

- #HTML, #CSS
- #PCRE #regexp
- #SQL
- #Math 😛

Others I learned or played with, and that I can probably pick up quickly:

- #Clojure
- #CPP
- #FSharp
- #OCaml

I should probably mention my non-native #English 🙂

Primarily, we're language learners 💪