Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!ark1!nems!mimsy!chris
From: chris@mimsy.umd.edu (Chris Torek)
Newsgroups: comp.lang.c
Subject: Re: printf
Message-ID: <20328@mimsy.umd.edu>
Date: 22 Oct 89 15:22:02 GMT
References: <28255@iuvax.cs.indiana.edu> <1989Oct21.234146.23275@utzoo.uucp>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 26

>In article <28255@iuvax.cs.indiana.edu> bobmon@iuvax.cs.indiana.edu
>(RAMontante) writes:
>>Henry Spencer and Chris Torek both tackle [printf("%d"+(a),b);] ...
>>... and the winner is --- CHRIS TOREK, by a score of 148 to 12!!!
>>(lines of response, that is)

:-)

In article <1989Oct21.234146.23275@utzoo.uucp> henry@utzoo.uucp
(Henry Spencer) writes:
>In fairness, Chris gave a much more detailed and precise discussion of
>the possible uncertainties in the interpretation of the code fragment.

Actually, what I intended to do (with unknown success) was encourage
people to think instead of just posting.  To that end, I posted something
outlining one way to think about the problem.

There has been, and no doubt will continue to be, a rash of postings
of the form `what does <x> do' for some simple but unusual <x> in
programming language <y>.  Most such questions are best answered by
looking in a good book about <y>, or in the standard for <y>.  (The
previous round was about e1[e2], in the form i[a] instead of a[i].)
-- 
`They were supposed to be green.'
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@cs.umd.edu	Path:	uunet!mimsy!chris