public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@aarsen.me>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: "Gcc" <gcc@gcc.gnu.org>,  joergboe <joergboe@snafu.de>,
	 vspefs <vspefs@protonmail.com>
Subject: Re: Generation of Make Dependencies for C++ Modules
Date: Sat, 27 Dec 2025 13:01:29 +0100	[thread overview]
Message-ID: <86qzsgp206.fsf@aarsen.me> (raw)
In-Reply-To: <878qeoqi9l.fsf@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 424 bytes --]

"Jose E. Marchesi" <jose.marchesi@oracle.com> writes:

> Not sure how relevant this is for C++, but soon we will be sending a
> proposal to Automake for supporting non-optional dependencies and thus
> having native support for Algol 68, Fortran and Go modules/packages.

C++ modules are in may ways similar to Fortran ones (but not entirely),
so it would be interesting to hear how that goes.
-- 
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 418 bytes --]

  reply	other threads:[~2025-12-27 12:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-22 18:11 joergboe
2025-12-23 16:23 ` Ben Boeckel
2025-12-25 18:28   ` joergboe
2025-12-26  3:16     ` Ben Boeckel
2025-12-27  5:50 ` vspefs
2025-12-27 11:24   ` Jose E. Marchesi
2025-12-27 12:01     ` Arsen Arsenović [this message]
2025-12-28  4:31     ` vspefs
2025-12-28 14:30       ` Jose E. Marchesi
2025-12-28 21:50         ` Nathaniel Shead
2025-12-29  0:03           ` vspefs
2025-12-29  2:31             ` Ben Boeckel
2025-12-29  6:12               ` vspefs
2025-12-29 16:13                 ` Ben Boeckel
2025-12-30 13:47                   ` vspefs
2025-12-30 16:19                     ` Ben Boeckel
2025-12-30 16:54                     ` Arsen Arsenović
2025-12-29  2:50         ` 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=86qzsgp206.fsf@aarsen.me \
    --to=arsen@aarsen.me \
    --cc=gcc@gcc.gnu.org \
    --cc=joergboe@snafu.de \
    --cc=jose.marchesi@oracle.com \
    --cc=vspefs@protonmail.com \
    /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).