Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!labrea!aurora!ames!ptsfa!ihnp4!inuxc!iuvax!pur-ee!j.cc.purdue.edu!k.cc.purdue.edu!l.cc.purdue.edu!cik
From: cik@l.cc.purdue.edu (Herman Rubin)
Newsgroups: comp.lang.misc,comp.lang.c,comp.lang.fortran,comp.lang.pascal
Subject: Names of non-local objects
Message-ID: <557@l.cc.purdue.edu>
Date: Fri, 24-Jul-87 12:05:45 EDT
Article-I.D.: l.557
Posted: Fri Jul 24 12:05:45 1987
Date-Received: Sat, 25-Jul-87 17:50:15 EDT
Reply-To: cik@l.cc.purdue.edu (Herman Rubin)
Distribution: world
Organization: Purdue University Statistics Department
Lines: 17
Xref: mnetor comp.lang.misc:579 comp.lang.c:3274 comp.lang.fortran:170 comp.lang.pascal:208

Many of us know the problems of linking programs produced by different
compilers, and of using external arrays or common blocks in such programs.
I propose that every language have a means of declaring a name used in
such a way as exact, that is the introduction of underlines is not done
in forming the object file.  This would enable the user who, for some reason,
wishes to combine programs from different compilers not to have to worry 
about what mangling of names is done by this compiler on this system.  In
fact, some of the systems at Purdue have their FORTRAN compilers pass the
names unchanged, and some use the (ugh!) prepending and postpending of
underlines.  This means that one cannot use the same combination of FARTRAN
and C source codes on the two machines.  The C programs are for a library
which is to be FORTRAN, as well as C, callable, and which cannot be written
in FORTRAN.
-- 
Herman Rubin, Dept. of Statistics, Purdue Univ., West Lafayette IN47907
Phone: (317)494-6054
hrubin@l.cc.purdue.edu or pur-ee!stat-l!cik or hrubin@purccvm.bitnet