edw@ius2.cs.cmu.edu.UUCP (04/08/87)
Have those of you whom have been all in an uproar about floating point ==, and parathesis reording ever think that C might not be the language for which your application is best suited. C seems to me to be oriented twords systems applications. There are valid reasons for allowing parathesis to be reordered in that contexted - the example of the macro expansion of putc or getc with other macros for one. And an example of where == is NEEDED for floating point variables and one that I have had to deal with is transferring floating point numbers from one machine over the network to another, where the floating point representations are not equivalent. Besides, I know of no language that forbids floating point equality comparisons. Why make C the first? Instead of changing the language to fit your application, why don't you find a language that is best fits your application. The only true flaw I've come up against in C is the fact that == is SO similiar to =. This bug has bitten me many of times. -- 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