Newsgroups: comp.object,comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!das-news.harvard.edu!news2.near.net!MathWorks.Com!europa.eng.gtefsd.com!howland.reston.ans.net!spool.mu.edu!torn!watserv2.uwaterloo.ca!undergrad.math.uwaterloo.ca!papresco
From: papresco@undergrad.math.uwaterloo.ca (Paul Prescod)
Subject: Re: Why Commit to Eiffel?
Message-ID: <Cw3FH6.LwK@undergrad.math.uwaterloo.ca>
Sender: news@undergrad.math.uwaterloo.ca (news spool owner)
Nntp-Posting-Host: cantor.math.uwaterloo.ca
Organization: University of Waterloo
References: <DERWAY.94Aug31155314@alumni.ndc.com> <779050720snz@wildcard.demon.co.uk> <DOUG.94Sep9075752@monet.ads.com> <MARCOXA.94Sep10111244@mosaic.nyu.edu>
Date: Wed, 14 Sep 1994 00:17:30 GMT
Lines: 17
Xref: glinda.oz.cs.cmu.edu comp.object:20403 comp.lang.lisp:14658

In article <MARCOXA.94Sep10111244@mosaic.nyu.edu>,
Marco Antoniotti <marcoxa@mosaic.nyu.edu> wrote:

>As long as it is C everything on a UN*X box is fine. As soon as you
>move to MSDOS or Windows things get hairy. You need a *Vendor* based
>`extern' declaration in order to link in other functions. For C++ the
>situation is even worse. It is conceivable that GNU G++ will never be
>able to link in Borland code, unless Borland decides to make public
>their complete demangling scheme (maybe they did - the issue here is
>not Borland).

Demangling is not the problem.  Completely different runtime architectures 
is.  There is no standard for _implementing_ exceptions, objects, RTTI,
even memory management.

Paul Prescod

