Path: utzoo!yunexus!geac!daveb
From: daveb@geac.UUCP (David Collier-Brown)
Newsgroups: comp.lang.c
Subject: Re: arrays...
Message-ID: <2706@geac.UUCP>
Date: 6 May 88 13:50:03 GMT
Article-I.D.: geac.2706
Posted: Fri May  6 09:50:03 1988
References: <5773@sigi.Colorado.EDU> <11325@mimsy.UUCP> <282@teletron.UUCP>
Reply-To: daveb@geac.UUCP (David Collier-Brown)
Organization: The large mumble department.
Lines: 30

| In article <11325@mimsy.UUCP>, chris@mimsy.UUCP (Chris Torek) writes:
| (Of course, if you add unnamed aggregates, you should also add
| unnamed functions.)

In article <282@teletron.UUCP> andrew@teletron.UUCP (Andrew Scott) writes:
| I was struck by Chris' comment, however.  How would unnamed functions be
| implemented?  How would they be used?  The { .. } syntax for aggregate declar-
| ations seems natural enough to use for unnamed aggregates, but how would it
| be done for functions?
| I'm just curious.  I can't think of how I would use this sucker.

 In smalltalk, all over the place. (ie, ifTrue [<unnamed-function>])
 In c, for passing to qsort....

	SYNTAX
             qsort(base, nel, width, compar)
             char *base;
             int (*compar)();

	EXAMPLE
             qsort(base, nel, width, { return zcomp($1,$2) });

	Note the problem with parameters...

--dave
-- 
 David Collier-Brown.                 {mnetor yunexus utgpu}!geac!daveb
 Geac Computers International Inc.,   |  Computer Science loses its
 350 Steelcase Road,Markham, Ontario, |  memory (if not its mind) 
 CANADA, L3R 1B3 (416) 475-0525 x3279 |  every 6 months.