Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!news.iecc.com!nerds-end From: Martin Ward Newsgroups: comp.compilers Subject: Re: Have we reached the asymptotic plateau of innovation in programming languages Date: Sun, 10 Jun 2012 10:42:05 +0100 Organization: Compilers Central Lines: 53 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <12-06-027@comp.compilers> References: <12-03-012@comp.compilers> <12-06-013@comp.compilers> <12-06-014@comp.compilers> NNTP-Posting-Host: news.iecc.com Mime-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: leila.iecc.com 1339394940 50010 64.57.183.58 (11 Jun 2012 06:09:00 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Mon, 11 Jun 2012 06:09:00 +0000 (UTC) Keywords: design Posted-Date: 11 Jun 2012 02:09:00 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:688 On Thursday 07 Jun 2012 at 18:21, "Johann 'Myrkraverk' Oskarsson" wrote: > Another point to make. Why do we assign from right to left? Is it in > any way natural? What's wrong with > > a + b --> c "a plus b assigned to c" > > instead of > > c <-- a + b "c becomes a + b?" > > The more I think about it, I believe the former construct is a bit more > natural since we read from left to right. However, I'd want to see or > work on a non-trivial project in such a language to make up my mind. It sounds like you want COBOL, which has: MOVE A TO B ADD A TO B GIVING C Or, if you want it the other way around: COMPUTE C = A + B You can also say: ADD A TO B which puts the result in B. On the other hand: MULTIPLY A BY B puts the result in A! Then there's: DIVIDE A BY B (or is it "DIVIDE A INTO B"?) My point is that by trying to be more "natural" and follow English language rules, rather than a concise and consistent set of rules, COBOL ends up with something verbose and inconsistent. -- Martin STRL Reader in Software Engineering and Royal Society Industry Fellow martin@gkc.org.uk http://www.cse.dmu.ac.uk/~mward/ Erdos number: 4 G.K.Chesterton web site: http://www.cse.dmu.ac.uk/~mward/gkc/ Mirrors: http://www.gkc.org.uk and http://www.gkc.org.uk/gkc