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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,44b0b57dd5d8f69 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,UTF8 Received: by 10.180.24.135 with SMTP id u7mr171683wif.3.1344572115059; Thu, 09 Aug 2012 21:15:15 -0700 (PDT) Path: n2ni53888063win.0!nntp.google.com!volia.net!news2.volia.net!feed-A.news.volia.net!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!feed.xsnews.nl!border-2.ams.xsnews.nl!news.panservice.it!aioe.org!.POSTED!not-for-mail From: "Vasiliy Molostov" Newsgroups: comp.lang.ada Subject: Re: List of Negative Language rules? Date: Sun, 05 Aug 2012 22:07:28 +0400 Organization: None Message-ID: References: NNTP-Posting-Host: Xw13RWgh8yxgPSv0x3+H9w.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: Opera Mail/12.01 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable Date: 2012-08-05T22:07:28+04:00 List-Id: Patrick =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(= =D0=B0) =D0=B2 =D1=81=D0=B2=D0=BE=D1=91=D0=BC =D0=BF=D0=B8=D1=81=D1=8C=D0= =BC=D0=B5 Sun, 05 = Aug 2012 18:39:42 +0400: > Does anyone happen to know if there is a list of negative language = > rules? If not I could try to re-read the book and compile a list. I = > think it would make for a good cheat sheet to paste to the wall to avo= id = > programming errors. Rationale should be a good reading. In general, a language element, being an universal atomic part of a mosa= ic = composed of such elements, provides you with ability to picture possibly= = any application, but to follow such universality each one should conform= = to some ruling. The thing here is similar to fractal seed definition. without such = definition a diversity of resulting fractals will not grow. This means = that you will restrict yourself in application design up to inability to= = express your desired application. To enumerate seeds with incorrect fractal definition (your case) you = should accept that their count can be close to equal to all possible = diversity of resulting fractals minus those are the correct ones and are= = what you have decided as appropriate to you. I dont know which is = appropriate to you, but suppose that Ada is appropriate too, and with Ad= a = rules you can get mostly working (meaningful) error-free application. With functions having out (or in out) parameters you will not be able to= = write expressions without side effects, since these will break elementar= y = algebra ruling, for example the order of evaluation becomes inconsistent= = with what you have wrote, and this gives you (and possibly another reade= r) = incorrect reading and ability to search these breaks forever, which is n= ot = you might want. Ada is aimed to prevent incorrect reading, e.g. a = 'readability' kind. BTW, you can still use 'access' type parameters in functions instead = (which is the same as 'in out'). ps. perhaps this is too abstruse, sorry for that. -- = =D0=9D=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE =D0=B2 =D0=BF=D0=BE=D1=87= =D1=82=D0=BE=D0=B2=D0=BE=D0=BC =D0=BA=D0=BB=D0=B8=D0=B5=D0=BD=D1=82=D0=B5= =D0=B1=D1=80=D0=B0=D1=83=D0=B7=D0=B5=D1=80=D0=B0 Opera: http://www.oper= a.com/mail/