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.2 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10a146,a03ae7f4e53958e1
X-Google-Attributes: gid10a146,public
X-Google-Thread: 1014db,a03ae7f4e53958e1
X-Google-Attributes: gid1014db,public
X-Google-Thread: 109fba,a03ae7f4e53958e1
X-Google-Attributes: gid109fba,public
X-Google-Thread: fac41,a03ae7f4e53958e1
X-Google-Attributes: gidfac41,public
X-Google-Thread: fa0ae,a03ae7f4e53958e1
X-Google-Attributes: gidfa0ae,public
X-Google-Thread: 1094ba,a03ae7f4e53958e1
X-Google-Attributes: gid1094ba,public
X-Google-Thread: 103376,8775b19e3c68a5dc
X-Google-Attributes: gid103376,public
X-Google-Thread: 114809,a03ae7f4e53958e1
X-Google-Attributes: gid114809,public
From: Guillermo Schwarz <gschwarz@netup.cl>
Subject: Re: Which language pays most? Smalltalk, not  C++ nor Java.
Date: 1997/12/27
Message-ID: <34A50CAA.54AA@netup.cl>#1/1
X-Deja-AN: 310522269
Content-Transfer-Encoding: 7bit
References: <199712121931.LAA25389@sirius.infonex.com>
 <67iipp$ktj$1@darla.visi.com> <882756127snz@genesis.demon.co.uk>
 <34A14C27.57C0@min.net> <67rjb3$pfb$1@brie.direct.ca>
Content-Type: text/plain; charset=us-ascii
Organization: NETup, Servicios Internet
Mime-Version: 1.0
Reply-To: gschwarz@netup.cl
Newsgroups: 
 comp.lang.fortran,comp.lang.c,comp.lang.c++,comp.lang.eiffel,comp.lang.java.programmer,comp.lang.smalltalk,comp.lang.perl.misc,comp.lang.ada,comp.edu
Date: 1997-12-27T00:00:00+00:00
List-Id: <comp.lang.ada>


Kaz Kylheku wrote:
> Although 'memcpy' is not a reserved keyword by any means,
> it is a reserved 'external name'. 
It is the first time I see reserved external.
> A strictly conforming program may not define any external
> name that begins with 'mem' followed by any combination of letters,
> digits or underscores. 
Ok. Define void memfoo() { } and see if it compiles.
It does.
> Define memcpy, if you write such a static function, you must not 
> include the <string.h> header in
> the same translation unit, else undefined behavior results.
Wrong. The compiler points out two different implementations.
The executable can't be generated.
> There is no such thing as ``overriding'' in C. Each external name must
> have exactly one definition if it is used anywhere in the program.
That's true. C is not object oriented. C++ is just an Smalltalk
wannabe.