Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/12/84; site desint.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!teddy!panda!talcott!harvard!seismo!hao!hplabs!sdcrdcf!trwrb!desint!geoff
From: geoff@desint.UUCP (Geoff Kuenning)
Newsgroups: net.lang.c
Subject: Re: unlimited length identifiers, and question about arrays of void fun()
Message-ID: <300@desint.UUCP>
Date: Fri, 11-Jan-85 04:57:53 EST
Article-I.D.: desint.300
Posted: Fri Jan 11 04:57:53 1985
Date-Received: Sun, 13-Jan-85 09:02:57 EST
References: <7079@brl-tgr.ARPA>
Organization: his home computer, Manhattan Beach, CA
Lines: 27

In article <7079@brl-tgr.ARPA> "Leigh L. Klotz"  writes:

>Instead of hacking the compiler to hash names, how about writing
>a program in C which grovels over the source files and produces an
>include file containing definitions like
>
>#define find_largest_mersenne_prime_unless_its_tuesday G00001
>
>which are included in every file in the make via the -I flag.

Um, you just ran yourself into the old PCC fixed-size-string-table problem.
If you try that trick on large programs, especially ones that already have
lots of #defines, the preprocessor will bomb on a string space overflow.
Pretty useful for small ones, though.

>Also, there was some discussion recently about arrays of pointers
>to functions returning void not working in PCC.  We've recently been
>bitten by this and I was wondering what the upshot of the discussion was.
>If there's a solution other than just not using void declarations on
>the functions, I'd like to hear about it.

I have been using -Dvoid=int except when I lint things.  Someday, when I get
a compiler that handles voids correctly, I'll take that out.
-- 

	Geoff Kuenning
	...!ihnp4!trwrb!desint!geoff