Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!ginosko!cg-atla!fredex
From: fredex@cg-atla.UUCP (Fred Smith)
Newsgroups: comp.lang.c
Subject: Re: This one bit me today
Message-ID: <7734@cg-atla.UUCP>
Date: 5 Oct 89 13:42:12 GMT
References: <2432@hub.UUCP>
Reply-To: fredex@cg-atla.UUCP (Fred Smith)
Organization: Agfa Compugraphic Division
Lines: 33

In article <2432@hub.UUCP> dougp@voodoo.ucsb.edu writes:
>-Message-Text-Follows-
>main()
>  {
>  int a=1,b=2,*p=&a,c;
>  c=b/*p;
>  }
>
>First real flaw in the C grammer I have found.




FLAME ON:

Just because C allows you to write terse, dense code, doesn't mean you should
actually DO it!

A much better (not to mention, more readable) way to write that would be:

c = b / *p;

or alternatively:

c = b / (*p);

With the second one you can leave out the spaces, which is your wont, even though
I think that it is easier to read with spaces around the operators and sub-expressions.

FLAME OFF:


Fred