kps

48 ms·

751.
by kps 3y ago
Unicode 1.0 Volume 2 Chapter 2 — https://www.unicode.org/versions/Unicode1.0.0/V2ch02.pdf
752.
by kps 3y ago
For grep, how much of the difference is due to '\w' having a different meaning between the two cases?
753.
by kps 3y ago
Thanks! I started working at a C compiler shop near the end of the '80s, and I don't recall knowing that this had been under way for so long already. (Though, we did freestanding targets, often with no conventional I/O, so lo
754.
by kps 3y ago
If a system supports Unicode, then wchar_t must be at least 21 bits, according to the C and C++ standards. Of course the 900lb gorilla has a 16-bit wchar_t, but the standards committees prefer to stick their fingers in their ears rather t
755.
by kps 3y ago
Too late to edit… the earliest relevant public reference I have found is https://groups.google.com/g/comp.lang.c/c/Tw-pMLfC52M/m/VQIm... including the phrase “a presentation of the issues involved
756.
by kps 3y ago
I know isspace() and the rest of ctype.h date to V7; I was wondering about locales specifically. I'm not aware of any pre-C89 implementation of anything similar to that, so I'm wondering whether X3J11 adopted it from some system I
757.
by kps 3y ago
My unverified assumption is that MacOS's behaviour here descends from NeXTStep, which used UCS-2.
758.
by kps 3y ago
The argument to `isspace()` (in that implementation) is a Unicode code point, not an encoding byte.
759.
by kps 3y ago
Did locales have any pre-existing implementation, or did X3J11 invent them?
760.
by kps 3y ago
C still does not require letters to be in order or contiguous. (In EBCDIC they're not contiguous.)
761.
by kps 3y ago
That's good to hear. If cross-platform sync is possible, passkeys are definitely a better option for the 95% of crud that currently lives in browsers' password managers.
762.
by kps 3y ago
That emphasized sentence is key. Pessimistically, it could mean that password managers can ‘save’ only to the Apple OS passkey store, acting as an intermediary transport, without being able to provide cross-platform vendor-agnostic sharing.
763.
by kps 3y ago
They're suited for delivery because they're based on video codecs (WebP on VP8, AVIF on AV1) for which consumer hardware typically has hardware decoding support, but were not designed for still images. AVIF is newer and substantia
764.
by kps 3y ago
Added in https://crrev.com/c/2749318
765.
by kps 3y ago
I think 12-bit colour stops it being adopted for ‘master’ images intended for editing. The current top comment says that 16-bit depth is a requirement for radiology. Also, I've read that its lossless encoding is often very poor — large
766.
by kps 3y ago
As an ‘operating system’ OS X includes user space tools like the Finder and Quick Look in particular where vendor support is helpful.
767.
by kps 3y ago
Excellent. JPEG XL is a usable general-purpose image format, not just a passive delivery format like WebP and AVIF.
768.
by kps 3y ago
Every nontrivial C++ project ends up picking a working subset, sometimes explicitly. These don't particularly correspond to standards versions. I ‘know C++’ according to coding standards X and Y pretty well, but I don't ‘know C++’
769.
by kps 3y ago
It's unfortunately not rare to find programs that write diagnostics to standard output instead of standard error.
770.
by kps 3y ago
Your OS version may vary (I'm not up to date) but look for ‘App Exposé’ in the Trackpad settings.
771.
by kps 3y ago
The main issue is that it adds validation code (if one is sticking to the standard) for things that don't care about UTF-16 at all. It does occupy 1/32 of the BMP, displaying a couple thousand potential actual characters (making t
772.
by kps 3y ago
Unification was reasonable at the time, given the goal to fit Unicode in 16 bits, and willingness to exclude obsolete characters. It's just that they followed official Japanese standards, and therefore unified too many from the point o
773.
by kps 3y ago
Naturally Unicode did the equivalent of colon-encoding too , for flags.
774.
by kps 3y ago
> Why should we expect invalid utf-16 strings to be representable in utf-8 or 32? We shouldn't care. UTF-16 should just be an encoding and its internal details shouldn't leak into Unicode code points. There's just no good
775.
by kps 3y ago
The UTF-32 equivalent is just the original UCS-4 — simply not enforcing any restrictions on the 32-bit value. Probably most code using UTF-32 does this, at least internally. (I can understand using high bits for metadata or non-Unicode po
776.
by kps 3y ago
From the C89 Rationale, “The potential for efficient code generation is one of the most important strengths of C. To help ensure that no code explosion occurs for what appears to be a very simple operation, many operations are defined to be
777.
by kps 3y ago
C89's ‘undefined behavior’ was a failed attempt to say “you get what the hardware gives you”.
778.
by kps 3y ago
Location: Kitchener/Waterloo, Ontario, Canada Remote: Yes (from Canada), or local office or hybrid. Willing to relocate: No Technologies: Systems software, broadly; experience with compilers and language tools, platform layers includin
779.
by kps 3y ago
It only has to be syntactically valid (parseable).
780.
by kps 3y ago
∇ is near-worst-case since it's not even Greek. I think domain-specific keyboard layouts are as much of a good idea as language-specific layouts, but they're a nuisance to install on *nix (trivial on OS X). Using .XCompose is the

More ›