🚀 go-pugleaf

In article <6173@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>In article <557@l.cc.purdue.edu> cik@l.cc.purdue.edu (Herman Rubin) writes:
>>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.
>
>There is a lot more to worry about than simply matching of external
>names by the linker.  Inter-language linkage can be quite tricky,...

Perhaps what we need is something more of the following form:
	#pragma interface_name c_name = external_name
Which would maker all uses of "c_name" in the C source show as "external_name"
in the linker.  This allows you to avoid the nasty assembly language step if
all you want is to avoid name convention problems (ie if a C call can be made 
"close enough", or a C procedure can cope with the others call format.)

This certainly fits smoothly in the language, since there is no need to use
this feature within a full C-world, and the "wart" stands out in a single 
place.

FROM:   Scott Daniels, Tektronix CAE
	5302 Betsy Ross Drive, Santa Clara, CA  95054
UUCP:   tektronix!teklds!cae780!daniels
	{ihnp4, decvax!decwrl}!amdcad!cae780!daniels 
        {nsc, hplabs, resonex, qubix, leadsv}!cae780!daniels