Path: csiph.com!1.us.feeder.erje.net!feeder.erje.net!1.eu.feeder.erje.net!news.szaf.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Ian Collins Newsgroups: comp.lang.c Subject: Re: Compiler design in C? Date: Thu, 10 Nov 2016 20:32:50 +1300 Lines: 24 Message-ID: References: <0915fef9-bb57-48b7-b98a-342f0e5ee39f@googlegroups.com> <87shr14n5b.fsf@gmail.com> <87r36k1l4w.fsf@gmail.com> <3e47c9bc-1c0a-40dc-9dc3-92e88ace6c31@googlegroups.com> <87lgwrzvqt.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net evgi4THlNB0alFg/Ql6rpA36YxK/d23gSqJN4tkGnh98Tb9zBw Cancel-Lock: sha1:mzDxApF76z0uSoqKDwt8zQBiU+s= User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 In-Reply-To: Xref: csiph.com comp.lang.c:96265 On 11/10/16 08:10 PM, Melzzzzz wrote: > On 2016-11-10, Gareth Owen wrote: >> Melzzzzz writes: >> >>> On 2016-11-09, BartC wrote: >>>> >>>> But how the hell do you do it with a std::string instead? You will also >>>> find the function name you want to call has been 'decorated'. >>>> >>>> Actually, I think there are problems even between different C++ compilers. >>>> >>> Lack of standardized C++ ABI is what makes C prefered choice for writing >>> interfaces for libraries that are callable from any language... >> >> This is idiotic. C++ makes it trivial to expose exactly the same library >> interface as you would in C. > > Bullshit. C++ makes a way to expose *C interface* not C++ interface. Nonsense, C++ makes it trivial to expose exactly the same library interface as you would in C: a C interface. -- Ian