jchd

IIRC the 16M limit is just an order of magnitude; the actual limit significantly depends on the volume of data.

Import in SQLite and apply any SQL magic massage needed to your data. You can just use the SQLite CLI (the command-line interface) with a memory (default) or disc-based database. You can define row and column separators if needed, .import the file as --csv, apply SQL to filter out unwanted rows, rewrite the resultant table to csv or whatever format you wish. If this operation turns to routine, store all these commands in a file and run it with the CLI. Use a recent sqlite3.exe, it's now full of rich features. Else slap a good regex in the face of the file!

You can remove the /gm options: nothing changes.

@pixelsearch is correct in pointing out that behavior. I don't have access to the C++ source for these functions, but notice that while SRE uses published PCRE v1 API, the "Replace" part in SRER is homebrew since there is no "replace" support API in PCRE v1. Yet AutoIt implementation of SRER matches legacy behavior of other PCRE v1 libraries. Play with this example, using Match or Substitute, $0 or $1: https://regex101.com/r/URSZPk/1

Correct, but I meant that ALL (100%) of GUI components use UTF16-LE internally. BTW, AutoIt is somehow limited to UCS2.

@lkjojfgfdg Windows has been natively supporting UTF16 since late XP.

Warning that subst-ed drives may point to non-root, soft and hard links as well.

Then I'd have said: "... for the rest of the day". 71 now, but I still can count for some time!

@pixelsearch you're right on 2) About 1) and (*X), that PCRE_EXTRA option is something you can ever use only after digging deep in PCRE code, only helpful in very VERY dark corner cases you should avoid at any rate. Hence # should be removed from the list in help. Omitting ) is a much bigger mistake, one which will haunt me for the rest of the year! BTW, I whish a peaceful 2026 to everyone in and, most importantly, outside the AutoIt community.

No big surprise here: when comparing raw codepoints AutoIt internals can make use of very fast machine instructions, while any regex engine has to dissect and compile the pattern and loop over the string & pattern. On the contrary, when it comes to process codepoints in any non-raw way or when the pattern isn't a bare string compare, regexes use very fast code using internal tables while AutoIt relies on Windows low-level primitives in a loop. Just tried a third compare run with regex including (*UCP) and the outcome is almost identical.

I only use SQLite for both personal and pro needs. I don't even use code (AutoIt or other) to manage my DBs: I run SQLite Expert Pro 24/7 and this covers 99.9% of my daily needs. The only extras I use are a handful of extensions I wrote (in C) to make my life easier.

Nice work, but regard timezones as a can of venimous snakes. General time keeping is even much, MUCH worse. tz data is only valid at a given point in time (how do you count time?) and for a loosely specified region. For example, look at https://time.is/fr/time_zone_news

The name you choose is a misnomer. "proper case" refers to capitalizing the first letter of each word in a sentence, like this: "Proper Case" Refers To Capitalizing The First Letter Of Each Word In A Sentence

Regexes can save your a$$ everyday!

You're perfectly right. Relevant neurons fixed!