From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,174ec7dc941a1068 X-Google-Attributes: gid103376,public,usenet X-Google-Language: ENGLISH,ASCII Path: g2news2.google.com!news4.google.com!out03b.usenetserver.com!news.usenetserver.com!in01.usenetserver.com!news.usenetserver.com!news.tele.dk!news.tele.dk!small.news.tele.dk!lnewsinpeer00.lnd.ops.eu.uu.net!bnewsinpeer00.bru.ops.eu.uu.net!emea.uu.net!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: Factory Pattern Newsgroups: comp.lang.ada User-Agent: 40tude_Dialog/2.0.15.1 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Reply-To: mailbox@dmitry-kazakov.de Organization: cbb software GmbH References: <1185387571.367570.163160@r34g2000hsd.googlegroups.com> <1185432247.046242.24300@o61g2000hsh.googlegroups.com> <1185439242.28126.36.camel@kartoffel> <1185447702.28126.57.camel@kartoffel> <1185454958.105983.143570@l70g2000hse.googlegroups.com> <1185541668.089363.258220@q75g2000hsh.googlegroups.com> <1185695674.206091.43870@w3g2000hsg.googlegroups.com> Date: Sun, 29 Jul 2007 10:53:49 +0200 Message-ID: NNTP-Posting-Date: 29 Jul 2007 10:53:35 CEST NNTP-Posting-Host: 52719047.newsspool1.arcor-online.net X-Trace: DXC=OGA@\YgN8h`016@cHD@m;jic==]BZ:afn4Fo<]lROoRaFl8W>\BH3Yb:P?e3KLE]DjDNcfSJ;bb[eIRnRBaCdmmm[?JB2:a:b X-Complaints-To: usenet-abuse@arcor.de Xref: g2news2.google.com comp.lang.ada:1260 Date: 2007-07-29T10:53:35+02:00 List-Id: On Sun, 29 Jul 2007 00:54:34 -0700, Maciej Sobczak wrote: > On 28 Lip, 00:23, "Randy Brukardt" wrote: > >> (New standards for other languages also will have to add >> this sort of support, or take their chances at having their standards fail.) > > When I think about it more, I cannot even believe it might be true. > Consider... C. It has the ISO standard and surely will be revised. > > One of the things that are taken for granted in the whole industry is > the fact that C names are immediately "extern" without any further > tweaking. Thanks to this you can write > > pragma Import (C, Puts, "puts"); > > and gain access to the standard puts function in C. Or any other. > *Every* programming language that is even remotely useful uses this > fact and relies on it. > > Now imagine that C introduces support for Unicode in names. In order > to reuse the whole existing infrastructure of binary utilities (the > tradition that is hard to drop) it would be necessary to introduce > name mangling that will translate Unicode identifiers into something a > typical linker can understand. But that will not be standardized, > leading to complete mess. The alternative would be to require that the > whole world starts to understand Unicode in symbol names for linking > and import/export. The implications for the industry would be > disastrous. > > My humble opinion: there will be no Unicode allowed for C identifiers > and the binary symbol names will stay Latin1 (or even a subset of it) > till the end of the world as we know it. This means that ISO cannot > have any reasonable mandate to enforce Unicode support on other > languages without the risk of undermining its credibility by being > inconsistent. > > Am I missing something? Hmm, AFAIK both C and C++ always mangled external names: "_puts" not "puts" in C. "??00puts@t346�$____�&G_Fsdf..." in C++. Usability is nobody's care, anyway. Just try to link Borland C++ to a MSVC import library, you'll see. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de