Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!adm!V4039%TEMPLEVM.BITNET@CUNYVM.CUNY.EDU
From: V4039%TEMPLEVM.BITNET@CUNYVM.CUNY.EDU (Stan Horwitz)
Newsgroups: comp.lang.c
Subject: Re: == vs =
Message-ID: <11220@brl-adm.ARPA>
Date: 12 Jan 88 03:00:54 GMT
Sender: news@brl-adm.ARPA
Lines: 15


  Yep, I completely agree with Mr. Lauff who offers some legitimate
rationale for having another symbol in place of "==".  It is not at all
unusual for symbols such as "=" to be misprinted or just smudged on high
speed line printers.  Why compound errors by having two such similar
operators?  I suggest the symbol => in place of ==.  It's such a nice,
unassuming symbol.  It's inclusion would not cause many problems even
for those compiling older programs.  As was said, all that is needed to
convert older programs' use of == to => is a global replace command in
your editor.  If your program is extremely large, then take a few minutes
to get a soda while your editor is making the change.  We all need an
occassional coffee (or soda) break.

Stan Horwitz
V4039 at TEMPLEVM.BITNET