Jump to content

jchd

MVPs
  • Posts

    9,916
  • Joined

  • Last visited

  • Days Won

    114

jchd last won the day on May 17 2025

jchd had the most liked content!

6 Followers

About jchd

  • Birthday 12/22/1954

Profile Information

  • Member Title
    Infinitely drawing infinity
  • Location
    South of France

Recent Profile Visitors

5,776 profile views

jchd's Achievements

  1. Correct, but I meant that ALL (100%) of GUI components use UTF16-LE internally. BTW, AutoIt is somehow limited to UCS2.
  2. @lkjojfgfdg Windows has been natively supporting UTF16 since late XP.
  3. Warning that subst-ed drives may point to non-root, soft and hard links as well.
  4. Then I'd have said: "... for the rest of the day". 71 now, but I still can count for some time!
  5. @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.
  6. 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.
  7. 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.
  8. 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
  9. 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
  10. Regexes can save your a$$ everyday!
  11. Wrong, the Bool datatype is clearly part of the language. Untrue as well. Perseverare diabolicum.
  12. That's plain wrong. Please reconsider! Local $v = 1=1 ConsoleWrite(VarGetType($v) & @LF)
  13. Indeed, all these buggy @DOUBLE_WS make this table terribly hard to read. Even copy-pasting the table content to a text editor and replacing @DOUBLE_WS by a couple of spaces doesn't align the columns. I confess being responsible for going deep into (*UCP) details in StringRegEx help (beside having authored the bulk of that help topic) but since we DO have AutoIt users handling cyrillic, greek, asian languages and others, I found it useful to mention everything of value for all users.
  14. No, its a small greek letter phi (φ). I was also surprised it existed. Got that source from @Nine (above) but didn't correctly check. Code fixed.
×
×
  • Create New...