mailing list of musl libc
 help / color / mirror / code / Atom feed
From: NRK <>
Subject: Re: [musl] [C23 string conversion 1/2] C23: implement the c8rtomb and mbrtoc8 functions
Date: Mon, 3 Jul 2023 07:37:44 +0600	[thread overview]
Message-ID: <20230703013744.ndlqmt3f662g6vwl@gen2.localdomain> (raw)
In-Reply-To: <>

On Sun, Jun 25, 2023 at 01:26:20PM -0400, Rich Felker wrote:
> A cleaner approach might be a union where the presence of the unsigned
> union member yields the alignment.

Slightly off-topic, but do you know if this is a standardized guarantee
or not?  While I'm aware that this works in practice - sometime ago I
was looking into the standard (c99 IIRC) to see if there's anything that
actually guarantees that or not and couldn't find anything concrete.


  parent reply	other threads:[~2023-07-03  1:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2023-05-31 14:01 ` Jens Gustedt
2023-06-25 17:26   ` Rich Felker
2023-06-26 10:28     ` Jₑₙₛ Gustedt
2023-07-03  1:37     ` NRK [this message]
2023-07-07 14:46       ` Markus Wichmann
2023-05-31 14:01 ` [musl] [C23 string conversion 2/2] C23: add the new include guards for string.h and wchar.h Jens Gustedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230703013744.ndlqmt3f662g6vwl@gen2.localdomain \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).