Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: James Kuyper Newsgroups: comp.lang.c Subject: Re: "A diagram of C23 basic types" Date: Mon, 7 Apr 2025 23:26:26 -0400 Organization: A noiseless patient Spider Lines: 19 Message-ID: References: <87y0wjaysg.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Tue, 08 Apr 2025 05:26:50 +0200 (CEST) Injection-Info: dont-email.me; posting-host="a82decdcecbf2be3578dae3b9c5284d3"; logging-data="1253508"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+ZKHB4hlpkwUvI4i/8V4vfmv2duu7Khlg=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:+9rXD+WcoDYCCU8s3eRai9ITFsE= In-Reply-To: Content-Language: en-US Bytes: 2276 On 4/7/25 22:39, Lawrence D'Oliveiro wrote: > On Fri, 4 Apr 2025 21:08:36 -0400, James Kuyper wrote: > >> There exist many programs that can compile either C code and C++ code, >> depending either upon the extension of the file name or explicit command >> line options to determine which language's rules to apply. > > But note that the *nix tradition is for the “cc” command to invoke nothing > more than a “driver” program, which processes each input file according to > its extension by spawning additional processes running the actual file- > specific processors. And these processors include the linker, for > combining object files created by the various compilers into an actual > executable (or perhaps a shared library). My point was that it doesn't matter if the same program can process C++ code, and also accepts VMTs when processing C code. The question was whether it accepts VMTs when processing C++ code. Whether it executes some other program to actually process the code, or does the processing itself, is irrelevant to that issue.