Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!cwjcc!gatech!bloom-beacon!bu-cs!buengc!bph
From: bph@buengc.BU.EDU (Blair P. Houghton)
Newsgroups: comp.lang.c
Subject: Re: A brace vs. indentation hypothesis (was Re: Braces are not Compiler-Fluff.)
Message-ID: <1880@buengc.BU.EDU>
Date: 12 Jan 89 17:45:56 GMT
References: <eWl9H#2cdgbS=eric@snark.UUCP> <272@twwells.uucp> <849@unh.UUCP> <9379@ihlpb.ATT.COM> <2695@ficc.uu.net>
Reply-To: bph@buengc.bu.edu (Blair P. Houghton)
Followup-To: comp.lang.c
Organization: Boston Univ. Col. of Eng.
Lines: 34

In article <2695@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes:
>Now me, I do this:
>
>	if (p != 0 &&
>	    p->barp != 0 &&
>	    p->barp->type == BAR_BAZ_TYPE)
>	{
>		debazify(p->barp);
>		saltpork(p);
>	}

I've added a bit below that makes the syntax of the above radically different,
and a red herring (maltjes, I think... :-) ):

Your mission, if you decide to accept it, is to imbed this smidgen of
code in the third include-file from the top and find the critical error
in the ten-seconds-before-yesterday your tyrannical boss gave you to do
it...

	if (p != 0 &&
	   p->barp != 0 &&
	   p->barp->type == BAR_BAZ_TYPE);
	{
		debazify(p->barp);
		saltpork(p);
		hungryrabbi(p);
	}

				--Blair
				  "Hint:  keep those braces as close
				   to their related syntactic element
				   as possible, or yer FIRED!.  Well, not
				   fired, per se, but I'll leave coding the
				   bitmaps for you to do..."