Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: $Revision: 1.6.2.13 $; site iuvax.UUCP
Path: utzoo!watmath!clyde!burl!mgnetp!ihnp4!inuxc!iuvax!brennan
From: brennan@iuvax.UUCP
Newsgroups: net.lang.c
Subject: Re: Re: 6 character external identifiers
Message-ID: <9500007@iuvax.UUCP>
Date: Wed, 11-Jul-84 14:58:00 EDT
Article-I.D.: iuvax.9500007
Posted: Wed Jul 11 14:58:00 1984
Date-Received: Fri, 13-Jul-84 02:53:49 EDT
References: <7804@umcp-cs.UUCP>
Lines: 22
Nf-ID: #R:umcp-cs:-780400:iuvax:9500007:000:715
Nf-From: iuvax!brennan    Jul 11 13:58:00 1984


Why not make the filter transparent to the user?
Make the standard 32 characters dualcase unique and let
the implementations that have sub-standard linkers use
a filter to map symbols.   Would this make symbolic
debugging that much harder??  I don't think so.
The Eunice C compiler does exactly this!  VMS allows
32 characters, but monocase.  And the mapping is not
very straightforward.

BufNameFree ->  BUFNAMEFREE_884000X
BufName	    ->  BUFNAMES_090000X

(I'll let you figure it on your own.)

I don't find this to be a problem when debugging.
And you have to do a lot of debugging under Eunice ;-)

JD Brennan
...!ihnp4!inuxc!iuvax!brennan	(USENET)
Brennan@Indiana			(CSNET)
Brennan.Indiana@CSnet-Relay	(ARPA)