> 3.243 Pathname
> [...] [...]
> is posix speak for '/'
But is that "Unicode codepoint 47" or "ASCII codepoint 0x2f" or
"whatever the character set in use provides that is a line between
upper right and lower left" or what? Does POSIX mandate an ASCII
superset, for example? C99 demands that
Date:Mon, 8 Nov 2021 13:47:09 -0500 (EST)
From:Mouse
Message-ID: <202111081847.naa28...@stone.rodents-montreal.org>
| What does POSIX say?
>From XBD (basic definitions)
3.243 Pathname
A string that is used to identify a file. In the context
of P
On Mon, Nov 08, 2021 at 03:30:14PM -0500, Mouse wrote:
> >> What does POSIX say?
> > [...]
> > 2. Each byte in the UTF-8 encoding is interpreted as ASCII
>
> As soon as any of the input codepoints are non-ASCII, UTF-8 generates
> octets which are ouside the ASCII range and thus cannot be interpret
>> What does POSIX say?
> [...]
> 2. Each byte in the UTF-8 encoding is interpreted as ASCII
As soon as any of the input codepoints are non-ASCII, UTF-8 generates
octets which are ouside the ASCII range and thus cannot be interpreted
as ASCII (at least not without further processing).
> 3. If the
> While most ASCII punctuation characters are legal in Unix filenames,
I actually would warn against some thinking that could be (not "is")
present here.
UNIX filenames are not character strings. They are octet strings,
which may be - often are - interpreted as encoding character strings.
Two oc
On Sat, Nov 06, 2021 at 09:42:04AM +, Taylor R Campbell wrote:
> Err... I don't think this will do what you want it to do. The effect
> will presumably be to add something like
>
> -Wl,-Bstatic -Wl,-Bdynamic ... -largon2
>
> to the linker command line eventually, because PROGDPLIBS ge
On 2021/11/06 18:42, Taylor R Campbell wrote:
--- /dev/null 1 Jan 1970 00:00:00 -
+++ sbin/cgdconfig/argon2_utils.c 6 Nov 2021 00:17:48 -
[...]
+ mem = usermem / 10;
What units are these in? Maybe add a comment explaining so the number
10 is a little more obvious?
