Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!athena.mit.edu!wesommer
From: wesommer@athena.mit.edu (William E. Sommerfeld)
Newsgroups: comp.lang.c
Subject: Re: Structure constants
Message-ID: <1554@bloom-beacon.MIT.EDU>
Date: Mon, 5-Oct-87 13:32:49 EDT
Article-I.D.: bloom-be.1554
Posted: Mon Oct  5 13:32:49 1987
Date-Received: Thu, 8-Oct-87 02:45:51 EDT
References: <843@usfvax2.UUCP> <667@its63b.ed.ac.uk>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: wesommer@athena.mit.edu (William E. Sommerfeld)
Organization: Massachusetts Institute of Technology
Lines: 15

In article <667@its63b.ed.ac.uk> simon@its63b.ed.ac.uk (Simon Brown) writes:
>In article <843@usfvax2.UUCP> chips@usfvax2.UUCP (Chip Salzenberg) writes:
>>I suggested that X3J11 include structure constants in the draft standard:
>Why leave it just at structure constants? Expanding it to arrays would be
>*much* more useful.
>
>You can't beat good honest anonymous data!

Why limit anonymity to data?  If you're going to do that, why not also
borrow a trick from Lisp, and include anonymous functions..

	qsort(array_int, sizeof(array_int)/sizeof(int), sizeof(int),
	      (int (*)(int *a, int *b)) { return *a-*b; });

				- Bill