Xref: utzoo comp.lang.c:8533 comp.lang.misc:1323
Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!cornell!rochester!PT.CS.CMU.EDU!IUS1.CS.CMU.EDU!edw
From: edw@IUS1.CS.CMU.EDU (Eddie Wyatt)
Newsgroups: comp.lang.c,comp.lang.misc
Subject: == vs. = a final word
Message-ID: <1222@PT.CS.CMU.EDU>
Date: 25 Mar 88 15:22:25 GMT
Sender: netnews@PT.CS.CMU.EDU
Organization: Carnegie-Mellon University, CS/RI
Lines: 13


 I thought I would add a final observation on the issue of ==  vs. =
and associated bugs.  I've come to the conclusion that simularity of
== and = is not at fault.   Neither is the feature that both may
appear within the same context.   It is the combination of features
that really compose the problem, not the individual components.
Any redesign should be evaluated against this flaw.  

Again this is not a proposal to change C, just a discussion of a misfeature.

-- 

Eddie Wyatt 				e-mail: edw@ius1.cs.cmu.edu