Path: ...!news.misty.com!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: "Chris M. Thomasson" Newsgroups: comp.lang.c Subject: Re: C23 thoughts and opinions Date: Fri, 7 Jun 2024 22:36:02 -0700 Organization: A noiseless patient Spider Lines: 43 Message-ID: References: <87msoe1xxo.fsf@nosuchdomain.example.com> <87ikz11osy.fsf@nosuchdomain.example.com> <20240607173657.984@kylheku.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sat, 08 Jun 2024 07:36:04 +0200 (CEST) Injection-Info: dont-email.me; posting-host="fcdc85211dd9fa312df49c2bc6e1985d"; logging-data="2623860"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/niKYoQUdBGb/dpHH2F84YYzXsmSgiqdM=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:aFvbKe/9FjgzEWNGgHubCF2Wvlw= In-Reply-To: Content-Language: en-US Bytes: 3373 On 6/7/2024 6:14 PM, bart wrote: > On 08/06/2024 01:39, Kaz Kylheku wrote: >> On 2024-06-07, bart wrote: >>> It's you who can't get your head around the idea that someone could be >>> away with a 'linker'. >> >> You can do away with linkers and linking. >> >> But it's pretty helpful when >> >> 1. the same library is reused for many programs. > > > You use a shared library. > >> 2. you're selling a library, and would like to ship a binary image of >> that library. > > You ship a shared library. > >> Without linkage, you don't have a library ecosystem. > > > Of course you do. Eg. a program depends on the vast WinAPI; but you > don't have to ship copies of all its DLLs, neither do you have to > statically link them. > > There are some fixups involving even with using dynamic linking. That's dynamic linking is linking? > taken care of by the OS loader. But the code involved isn't extensive. > Here is an 800-line C program: > >   https://github.com/sal55/langs/blob/master/runmx.c > > that loads a private executable format of mine; it loads any dynamic > libraries also in the same format (but it doesn't multiple instances > with other processes); and it resolves any symbols from dependent DLLs. > Then it runs the program. > > (Here written using WinAPI calls.)