From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,1116ece181be1aea X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-09-25 04:29:38 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!arclight.uoregon.edu!wn13feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi_feed4!attbi.com!sccrnsc04.POSTED!not-for-mail From: "Jeff C," Newsgroups: comp.lang.ada References: <3F650BBE.4080107@attbi.com> <3F67AAC6.2000906@attbi.com> <3F7024F8.1000102@crs4.it> <3F71A78A.5000701@crs4.it> Subject: Re: Is the Writing on the Wall for Ada? [although this thread changed to something else a long time ago] X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: NNTP-Posting-Host: 66.31.4.164 X-Complaints-To: abuse@comcast.net X-Trace: sccrnsc04 1064489377 66.31.4.164 (Thu, 25 Sep 2003 11:29:37 GMT) NNTP-Posting-Date: Thu, 25 Sep 2003 11:29:37 GMT Organization: Comcast Online Date: Thu, 25 Sep 2003 11:29:37 GMT Xref: archiver1.google.com comp.lang.ada:42884 Date: 2003-09-25T11:29:37+00:00 List-Id: "Vinzent 'Gadget' Hoefler" wrote in message news:bkubhj$5v7t7$1@ID-175126.news.uni-berlin.de... Russ wrote: >just basic common sense. Let me ask you which of the following is more >readable: > >lwienfowowoenfnowoqndfoowopqihjefhnowqoowldvno := > lwienfowowoenfnowoqndfoowopqihjefhmowqoowldvno + 1 > >or > >lwienfowowoenfnowoqndfoowopqihjefhnowqoowldvno += 1 They are not equivalent. Using basic common sense, I'd say, the first one assigns the sum of lwienfowowoenfnowoqndfoowopqihjefhmowqoowldvno and 1 to lwienfowowoenfnowoqndfoowopqihjefhnowqoowldvno, whilst the second one just adds 1 to lwienfowowoenfnowoqndfoowopqihjefhnowqoowldvno itself. One lesson learned: You really should take care of your variable's names. :) Yipes! I think you just made the point that the C++ syntax is less error prone...Now this mis-named thread will never die.