public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Boris Kolpackov <boris@codesynthesis.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: Ben Boeckel <ben.boeckel@kitware.com>, gcc@gcc.gnu.org
Subject: Re: [modules] Preprocessing requires compiled header unit modules
Date: Mon, 25 Apr 2022 11:20:13 +0200	[thread overview]
Message-ID: <boris.20220425111008@codesynthesis.com> (raw)
In-Reply-To: <EAAF2C2C-6A18-4534-AD5A-B3CEE7EF48CD@sandoe.co.uk>

Iain Sandoe <iain@sandoe.co.uk> writes:

> The standard has the concept of an “importable header” which is
> implementation-defined.

But it must contain all the C++ library headers:

https://eel.is/c++draft/headers#4


> We could choose that only headers that are self-contained (i.e. unaffected
> by external defines) are “importable” (thus the remaining headers would
> not be eligible for include-translation). That would mean that we could
> rely on processing any import by processing the header it is created from?
> Perhaps that is too great a restriction and we need to be more clever.

It will also be hard to determine whether the header (or any header
that it includes) satisfies this condition. You would probably want it
to be "meaningfully self-contained" (since pretty much every header is
not self-contained with regards to include guards) which I think will
be hard to automate.

  reply	other threads:[~2022-04-25  9:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 23:46 Ben Boeckel
2022-04-21  4:05 ` Boris Kolpackov
2022-04-21 12:05   ` Ben Boeckel
2022-04-21 17:59     ` Iain Sandoe
2022-04-21 18:08       ` Ben Boeckel
2022-04-21 18:18         ` Iain Sandoe
2022-04-22 14:08     ` Boris Kolpackov
2022-04-22 15:06       ` Iain Sandoe
2022-04-25  9:20         ` Boris Kolpackov [this message]
2022-04-22 16:05       ` Ben Boeckel
2022-04-25  9:42         ` Boris Kolpackov
2022-04-25 11:34           ` Ben Boeckel

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=boris.20220425111008@codesynthesis.com \
    --to=boris@codesynthesis.com \
    --cc=ben.boeckel@kitware.com \
    --cc=gcc@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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. 
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 read-only IMAP folder(s) and NNTP newsgroup(s).