🚀 go-pugleaf

Warner Losh (imp@village.org) wrote:
|> In article <3vo9lr$los@metro.ucc.su.oz.au>,
|> John Max Skaller <maxtal@Physics.usyd.edu.au> wrote:
|> >	It isn't clear it is POSSIBLE to use qsort.
|> >Suppose extern "C" functions use a DIFFERENT calling convention.

|> This sounds like another of the committee's unwise calls.  I do
|> understand the issues behind it, however, there is some legacy code
|> that depends on being able to call qsort from C++.

|> >	Result: qsort may not be useable: it has to be there,
|> >it doesn't have to be useful. You certainly can't assume at this
|> >point in time any use of it will be portable. The final Standard
|> >might provide better guarrantees, but I have doubts.

|> This is the part that worries me the most.  Traditionally, you've been
|> able to do this, and as far as I know it works on all existing
|> compilers (at least the major ones I've used).  Breaking this now
|> isn't the best possible service that the committee could do to the
|> application developers (although it does let the compiler writers off
|> the hook more easily).

It wasn't supported by the Zortech compilers under MS-DOS.  C and C++
used different linkage conventions.
-- 
James Kanze           (+33) 88 14 49 00          email: kanze@gabi-soft.fr
GABI Software, Sarl., 8 rue des Francs Bourgeois, 67000 Strasbourg, France
Conseils en informatique industrielle--
                             --Beratung in industrieller Datenverarbeitung