Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!seismo!harpo!eagle!mit-vax!grkermit!genrad!wjh12!n44a!ima!inmet!bhyde
From: bhyde@inmet.UUCP
Newsgroups: net.lang.c
Subject: Re: Orphaned Response - (nf)
Message-ID: <771@inmet.UUCP>
Date: Tue, 24-Jan-84 05:42:51 EST
Article-I.D.: inmet.771
Posted: Tue Jan 24 05:42:51 1984
Date-Received: Sat, 28-Jan-84 00:54:33 EST
Lines: 31

#R:vaxine:-15200:inmet:5000010:177600:1150
inmet!bhyde    Jan 22 17:25:00 1984


This will work; f1, f2, and f3 are necessary.  Of course I didn't want
to have f1, f2, and f3, but then it occurs to me that this isn't Ada
and suddenly I am happy.
						Ben Hyde, Intermetrics Inc.

typedef int elem;  		/* An element				     */
typedef elem feature_vec[];	/*   held in an array     		     */
typedef feature_vec *features;	/*	with pointers to those arrays        */
typedef features ftable[];	/*         which are themselfs in an array.  */

feature_vec f1 = {1,2,2,0};
feature_vec f2 = {2,3,0};
feature_vec f3 = {2,4,0};
ftable success = { (features)f1, (features)f2, (features)f3};
	/* the casts are necessary or one gets warnings, why I don't know */

The zero element is being used here to mark the ends of a feature_vec, analogous
to the zero element at the end of a string.

Sam Haradhvala, my coworker here, said that in his application the
ftable success was automaticly generated  and that the set of all f1,
f2, f3... overflowed one of the many target machine linkers.  In such
cases one can do:
feature_vec f1 = {1,2,2,0,
		 ,2,3,0,
		 ,2,4,0};
ftable success = { (features)&f1[0], (features)&f1[4], (features)&f1[7]};