Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!indri!lll-winken!uunet!pilchuck!dataio!bright
From: bright@Data-IO.COM (Walter Bright)
Newsgroups: comp.lang.c++
Subject: Re: extern "language" (was: C --> C++)
Message-ID: <1969@dataio.Data-IO.COM>
Date: 8 May 89 18:05:48 GMT
References: <2857@pegasus.ATT.COM> <2858@pegasus.ATT.COM>
Reply-To: bright@dataio.Data-IO.COM (Walter Bright)
Organization: Data I/O Corporation; Redmond, WA
Lines: 21

In article <2858@pegasus.ATT.COM> ech@pegasus.ATT.COM (Edward C Horvath) writes:
<From article <2857@pegasus.ATT.COM<, by hansen@pegasus.ATT.COM (Tony L. Hansen):
<< By the way, the next version of Zortech's C++ compiler will also support the
<< 	extern "Pascal"
<< linkage specification, in addition to the extern "C" and "C++" linkage
<< specifications.
<How nice; I'd hope that Apple's announced (shipping delta days after AT&T
<ships) MPW cfront will also support 'extern "pascal"':

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.