Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!quintus!ok
From: ok@quintus.uucp (Richard A. O'Keefe)
Newsgroups: comp.lang.c
Subject: Re: "Numerical Recipes in C" is nonport
Message-ID: <470@quintus.UUCP>
Date: 23 Sep 88 09:40:36 GMT
References: <5162@hoptoad.uucp> <225800072@uxe.cso.uiuc.edu> <4071@bsu-cs.UUCP>
Sender: news@quintus.UUCP
Reply-To: ok@quintus.UUCP (Richard A. O'Keefe)
Organization: Quintus Computer Systems, Inc.
Lines: 18

In article <4071@bsu-cs.UUCP> dhesi@bsu-cs.UUCP (Rahul Dhesi) writes:
>In article <225800072@uxe.cso.uiuc.edu> mcdonald@uxe.cso.uiuc.edu writes:
>[re linkers with 6-char limit]
>Actually, it's even easier than that.  The C compiler can generate an
>internal object format.  A custom post-processor takes these object
>files, scans for all long identifiers, shortens them to unique 6-char
>names, and produces as its output system-format object files ready for
>the standard linker.  No linking need be done by this post processor.

There are several reasons why one wants the names in the source code to
bear a simple predictable relation to the names the system sees, such as
mixed language programming and system-supplied debugging tools like load
maps.  The people in comp.lang.c++ often complain about compiler-
generated names.

There was a program posted to one of the sources news-groups a while back
that did the long name -> unique name mapping on the source code; sorry I
can't remember the name or the date, ask in comp.sources.wanted.