From 2374299714050049848 X-Google-Thread: f78e5,b53358bee20fa31 X-Google-Attributes: gidf78e5,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail NNTP-Posting-Date: Wed, 12 Dec 2007 15:25:43 -0600 Return-Path: X-Virus-Scanned: amavisd-new at csse.unimelb.edu.au X-Authentication-Warning: mulga.csse.unimelb.edu.au: fjh set sender to devnull@stump.algebra.com using -f X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov) X-Virus-Scanned: amavisd-new at csse.unimelb.edu.au X-Original-To: std-c++@mailman.ucar.edu Delivered-To: std-c++@mailman.ucar.edu X-SMTP-Auth: no X-Authentication-Warning: serv2.gc.ams.giganews.com: news set sender to poster@giganews.com using -f From: Francis Glassborow User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 Subject: Re: Proposal for ISO C/C++: Extensions for Portable Compilation and Linkage References: <16b078ea-6736-44f3-bdbf-d8d062b63ac1@d21g2000prf.googlegroups.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: X-AuthenticatedUsername: NoAuthUser X-Complaints-To: abuse@btinternet.com X-DMCA-Complaints-To: abuse@btinternet.com X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.36 Newsgroups: comp.std.c++ X-Virus-Scanned: amavisd-new at ucar.edu Approved: Fergus Henderson , moderator of comp.std.c++ Date: Wed, 12 Dec 2007 15:29:21 CST Lines: 43 X-Usenet-Provider: http://www.giganews.com X-Trace: sv3-imsK+lVHuoRrqFvBee9OK4Y6gERvVRJMoTtFb5Ie6Kk55WfgOQZtmKdxuohskXMzsWJ/Zr4qRCFc0RB!R/N5qdzYWjIkhU0Shi1RBk/VkjesuK9XMkY8RMJB5A15xxwi+tyf53I0 X-Complaints-To: abuse@giganews.com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.36 Xref: g2news1.google.com comp.std.c++:9805 Andre Kaufmann wrote: > Sean Hunt wrote: >> On Dec 11, 11:09 am, akfmn...@t-online.de (Andre Kaufmann) wrote: >> [...] >> If you read N2425, you'll find that it goes even further, proposing: > > Thank you for the hint, Sean. > But I'm still missing specifications for dynamic binary linkage. That > shouldn't be perhaps part of the C++ standard, but another one > specifying dynamic binary linkage compatibility between C and C++ > compilers. > > So that you take a library written with compiler A and simply write > > #import "LibraryA.so" > #import "LibraryA.dll" > > and the compiler B compiles and links the code either dynamically or > perhaps even statically, without the need of header files etc. > > It might be a problem for exporting C++ objects, but at least the name > mangling for flat functions could be standardized. If the compiler > additionally stores meta information for used structures and variables > you could simply use the library with every C and C++ compiler. > > It's perhaps not a big problem in the Open Source world, but for closed > source libraries. > No, it is not that simple. You cannot even do it for C TU's compiled with different compilers unless there is an ABI for the platform you are using. It isn't just name-mangling that matters but other linkage details as well as the size and organisation (little-endian, big-endian etc) of the built-in types. And then we come to issues about how to support both virtual functions and virtual bases. And so it goes on ... --- [ comp.std.c++ is moderated. To submit articles, try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://www.comeaucomputing.com/csc/faq.html ]