Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rochester!pt.cs.cmu.edu!ius2.cs.cmu.edu!edw
From: edw@ius2.cs.cmu.edu (Eddie Wyatt)
Newsgroups: comp.lang.c
Subject: Parenthesis
Message-ID: <1100@ius2.cs.cmu.edu>
Date: Sun, 12-Apr-87 16:46:46 EST
Article-I.D.: ius2.1100
Posted: Sun Apr 12 16:46:46 1987
Date-Received: Sun, 19-Apr-87 09:38:27 EST
Distribution: na
Organization: Carnegie-Mellon University, CS/RI
Lines: 40


    I haven't seen any other postings about compiler control lines to
control optimization. Something like :

#sacred		:-)
    a = (b + c) + f;
#endsacred 


  Seriously I think this has been the best proposal yet.  It has no
affect on existing code and seems to allow the most flexiblity
over what parts of the code may be optimized.

    I like the fact that the C compiler optimizes my code to a degree
for me.  I don't have to rewrite expressions like xbar = x - 0.0  to 
xbar = x and angle = (PI/180.0)*x/2.0 to angle = (PI/360.0)*x.
Why would I write code like this in the first place. Take a look
at a previous posting I made with a set of macros that I do use.

   I am not totally insensitive to the complaints the numerically analysis
people are giving.  I do think that the unitary '+' is an awlful hack to
the problem.  In turn though, I do not think the number crunching
community has been listening to the complaints of us speed oriented
programmers.   The types of applications that I am dealing with
are autonomous vehicles where every millisecond counts.


-- 
					Eddie Wyatt

They say there are strangers, who threaten us
In our immigrants and infidels
They say there is strangeness, too dangerous
In our theatres and bookstore shelves
Those who know what's best for us-
Must rise and save us from ourselves

Quick to judge ... Quick to anger ... Slow to understand...
Ignorance and prejudice and fear [all] Walk hand in hand.
					- RUSH