Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ukma!rutgers!att!pegasus!hansen
From: hansen@pegasus.ATT.COM (Tony L. Hansen)
Newsgroups: comp.lang.c++
Subject: Re: extern "language" (was: C --> C++)
Summary: the word from above
Keywords: extern "language"
Message-ID: <2865@pegasus.ATT.COM>
Date: 9 May 89 02:53:07 GMT
References: <2857@pegasus.ATT.COM> <2858@pegasus.ATT.COM> <1969@dataio.Data-IO.COM>
Reply-To: hansen@pegasus.ATT.COM (Tony L. Hansen)
Organization: AT&T Bell Laboratories, Lincroft, NJ, USA
Lines: 29

< It's case sensitive, according to Bjarne's wishes. Thus, it's:
<	"C"
<	"C++"
<	"Pascal"	// Capitalized 'cuz C and C++ are
< Let's be consistent from the outset, to avoid silly annoyances. I'll be so
< bold as to also propose:
<	"Fortran"
< for those compilers so capable. Let's all avoid the mess that #pragma's
< are sinking into.
<
< This is a much better solution than the clumsy 'cdecl' and 'pascal'
< keywords cluttering up things.

In Bjarne's latest draft C++ Reference Manual, he states:

>> Where the name of a programming language is used to name a style of
>> linkage in the string in a linkage-specification, it is recommended that
>> the spelling be taken from the document defining that language. For
>> example, Ada (not ADA) and FORTRAN (not Fortran).

This means that "Pascal" is correct, as will be the names "Modula-2", "PL/I"
(oh no!), "Eiffel", "BASIC" (double oh no!), "COBOL" (it keeps getting
worse, doesn't it?), "Smalltalk-80", "Objective-C", and so on.

Sorry Walter, you've been out voted.

					Tony Hansen
				att!pegasus!hansen, attmail!tony
				    hansen@pegasus.att.com