Deutsch English Français Italiano |
<v4mudn$3jg8$2@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: David Brown <david.brown@hesbynett.no> Newsgroups: comp.lang.c Subject: Re: C23 thoughts and opinions Date: Sun, 16 Jun 2024 16:55:51 +0200 Organization: A noiseless patient Spider Lines: 13 Message-ID: <v4mudn$3jg8$2@dont-email.me> References: <v2l828$18v7f$1@dont-email.me> <00297443-2fee-48d4-81a0-9ff6ae6481e4@gmail.com> <v2lji1$1bbcp$1@dont-email.me> <87msoh5uh6.fsf@nosuchdomain.example.com> <f08d2c9f-5c2e-495d-b0bd-3f71bd301432@gmail.com> <v2nbp4$1o9h6$1@dont-email.me> <v2ng4n$1p3o2$1@dont-email.me> <87y18047jk.fsf@nosuchdomain.example.com> <87msoe1xxo.fsf@nosuchdomain.example.com> <v2sh19$2rle2$2@dont-email.me> <87ikz11osy.fsf@nosuchdomain.example.com> <v2v59g$3cr0f$1@dont-email.me> <87plt8yxgn.fsf@nosuchdomain.example.com> <v31rj5$o20$1@dont-email.me> <87cyp6zsen.fsf@nosuchdomain.example.com> <v34gi3$j385$1@dont-email.me> <874jahznzt.fsf@nosuchdomain.example.com> <v36nf9$12bei$1@dont-email.me> <87v82b43h6.fsf@nosuchdomain.example.com> <v4kdmu$3hi90$1@dont-email.me> <v4l547$3lqic$6@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sun, 16 Jun 2024 16:55:51 +0200 (CEST) Injection-Info: dont-email.me; posting-host="efa9642fc1579e8fdfcdda80d78f3954"; logging-data="118280"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/w14Kn812bK79gGepCRd3hqWKOWkbAZV0=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:qvgj3qjIFFphQF7odvkZAlBtHEc= In-Reply-To: <v4l547$3lqic$6@dont-email.me> Content-Language: en-GB Bytes: 2308 On 16/06/2024 00:37, Lawrence D'Oliveiro wrote: > On Sat, 15 Jun 2024 17:58:22 +0200, David Brown wrote: > >> But it also seems reasonable to expect that if a file is big enough to >> cause trouble for #embed, then any other method of including it in a C >> file will be at least as bad and probably /much/ worse. > > But if you redefine the problem as “any method of including it in a C > *program*”, then you realize that there are better techniques that do not > involved C extensions. Yes, as I said.