JdeBP<p><span class="h-card" translate="no"><a href="https://mastodon.social/@cks" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>cks</span></a></span> </p><p>Warning: rabbit hole</p><p><a href="https://polymaths.social/@rl_dane/statuses/01K1XR4D4GCKDD7PQMSRAMV5EA" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">polymaths.social/@rl_dane/stat</span><span class="invisible">uses/01K1XR4D4GCKDD7PQMSRAMV5EA</span></a></p><p>You'll recognize this one as well, no doubt. There's probably an old Usenet FAQ somewhere with it, although I haven't checked.</p><p>But it got me to thinking of when the idea of a-z collating *entirely after* A-Z became a norm; only to falter again when ASCII systems met other countries. When the era was.</p><p>I checked with a couple of my old printed dictionaries from the 20th century, and they had case-insensitive collation in English. One even put 'a' ahead of 'A'.</p><p>It's definitely thus an <a href="https://mastodonapp.uk/tags/ASCII" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ASCII</span></a> notion, but did it pre-date <a href="https://mastodonapp.uk/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Unix</span></a>? Did it pre-date regular expression syntax? Or shell globbing?</p><p>My initial educated guess would be that the golden period of A-Za-z was the middle 1960s with ASCII and some Unix predecessor to the early 1990s when all of the books/posts/whatnot on the new Standard C were spreading the knowledge of locales.</p><p><a href="https://mastodonapp.uk/tags/UnixHistory" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnixHistory</span></a> <a href="https://mastodonapp.uk/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>retrocomputing</span></a> <a href="https://mastodonapp.uk/tags/locales" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>locales</span></a> <a href="https://mastodonapp.uk/tags/collation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>collation</span></a> <a href="https://mastodonapp.uk/tags/RegularExpressions" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RegularExpressions</span></a> <a href="https://mastodonapp.uk/tags/fnmatch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fnmatch</span></a></p>
#regularexpressions
0 posts0 participants0 posts today
Weekend reading for code obsessives, based on my current work adding semi-full regular expressions to Quamina. Two blog entries, coding recommendation, and a quiz/challenge.
1. QRS: Quamina Regexp Series - https://www.tbray.org/ongoing/When/202x/2024/12/12/Quamina-Regular-Expression-Series
2. QRS: Parsing Regular Experssions - https://www.tbray.org/ongoing/When/202x/2024/12/12/QRS-Parsing-Regular-Expressions
[If you don’t know what a “regular expression is”, please ignore this, and don’t feel bad, because nobody should have to know that.]
I already knew of this #regex that tests for #PrimeNumbers but in case you haven’t, then you’re one of the lucky (#xkcd) 10000!
Replied in thread
I just finished another war against RegEx... Anyone else know the feeling?
#regex #infosec #development #programming #RegularExpressions
(Updated picture to make it say O RLY)
On .NET | Deep Dive into RegEx with Stephen Toub & Scott Hanselman.
#dotnet #regularexpressions #regex #programming
https://www.youtube.com/watch?v=ptKjWPC7pqw&ab_channel=dotnet
Replied in thread
@trochee
It's gratifying to see you making fun of stuff I never got around to learning.
#RegularExpressions #Perl
Developers: how do you personally pronounce "regex"?
* Rej-ex ("Rej" as in "register")?
* Reg-ex ("Reg" as in "regular")?
* Something different? - share in the comments!
Any #RakuLang core hackers want to take up this challenge?
#RegularExpressions #RegExps #RegExes #RegEx https://ruby.social/@gd/110718818730295923
Ruby.socialGreg Donald :ruby: :whyfox: (@gd@ruby.social)Q. What do we want?
A. Raku-compatible Regular Expressions (RCRE™)
Q. When do we want it?
A. 25 years ago? 😂
#Perl #Raku
https://docs.raku.org/language/regexes
Replied in thread
@smonff @Perl Y’all know I’m the first to crow about unique #Perl features, but #RegularExpressions’ syntax of ^ for the start of a line or string and $ for the end dates back at least to #Unix co-author Ken Thompson’s rewrite of the `qed` text editor for the #CTSS operating system on the IBM 7090 #mainframe at #BellLabs around 1970. (Perl creator Larry Wall was a teenager at the time.)
A useful little site for testing the equivalence of two regular expressions:
https://bakkot.github.io/dfa-lib/regeq.html
(Source code: https://github.com/bakkot/dfa-lib)
PS. Speaking of regular expressions, I’m sure you‘re all familiar with RegExr so I’m not even mentioning that… Well, I guess I am ;) https://regexr.com/
bakkot.github.ioRegEq
Replied in thread
@jens @stoerdebegga Most #Perl readability complaints are actually about #RegularExpressions, which every other worthwhile language has as well. Perl’s #regexp support happens to be first-class, and consequently, It has the best tools for regexp readability.
If you see Perl that does not use those tools, that is a failure of the programmer and not the language.
Replied in thread
@sjn @cb 99% of the “#Perl is line noise” complaints are because of unformatted #RegularExpressions. Every language worth anything eventually supports them, but only @Perl (and #awk, earlier) makes them first-class citizens. And with Perl you can format and comment them for readability: https://perldoc.perl.org/perlretut#Embedding-comments-and-modifiers-in-a-regular-expression
We format the rest of our code for humans. Why not #regexps?
#PerlCritic can warn against bad regexps: https://metacpan.org/search?size=200&q=module%3APerl%3A%3ACritic%3A%3APolicy%3A%3ARegularExpressions
perldoc.perl.orgperlretut - Perl regular expressions tutorial - Perldoc Browser
Replied in thread
@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
www.pcre.orgpcre2compat specification
#RegularExpressions #JavaScript:
Putting a question mark after a quantifier such as {1,3} or * or + makes that quantifier _reluctant_—it matches as little as possible:
> /^(#{1,3}?)(#*)$/.exec('####').slice(1,3)
[ '#', '###' ]
> /^(#{1,3})(#*)$/.exec('####').slice(1,3)
[ '###', '#' ]
https://exploringjs.com/impatient-js/ch_regexps.html#quantifiers
exploringjs.comRegular expressions (`RegExp`) • JavaScript for impatient programmers (ES2022 edition)
ECMAScript proposal: RegExp flag `/v` makes character classes and character class escapes more powerful
https://2ality.com/2022/11/regexp-v-flag.html
#EsNextNews #EcmaScript #JavaScript #RegularExpressions
2ality.comECMAScript proposal: RegExp flag `/v` makes character classes and character class escapes more powerfulIn this blog post, we look at the ECMAScript proposal “RegExp v flag with set notation + properties of strings” by Markus Scherer and Mathias Bynens.
Habe gerade rausgefunden, wie man die remote_follow-URL mit RegEx findet.
Super nützlich, wenn man #neuhier wie ich ist und eine Passwortmanager mit Unterstützung für "Reguläre Ausdrücke" aka #regularexpressions (RegEx) hat, um die URL zu prüfen.
Remote-Follow Domain: https://SUBDOMAIN.TLD/users/NUTZERNAME/remote_follow
#RegEx für die Domain:
^https:\/\/\S+\/users\/\S+\/remote_follow$
P.S. Mir hat https://regexone.com geholfen.