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,ac4955b8006bd13c X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.238.65 with SMTP id vi1mr15501696pbc.7.1338955837541; Tue, 05 Jun 2012 21:10:37 -0700 (PDT) Path: l9ni10887pbj.0!nntp.google.com!news1.google.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail From: Shark8 Newsgroups: comp.lang.ada Subject: Re: Q: type ... is new String Date: Tue, 5 Jun 2012 21:09:17 -0700 (PDT) Organization: http://groups.google.com Message-ID: References: <82defba0-2d39-4418-b678-ebbefeb105d7@x21g2000vbc.googlegroups.com> <4fcccd1f$0$6583$9b4e6d93@newsspool3.arcor-online.net> <4fccdd0c$0$6578$9b4e6d93@newsspool3.arcor-online.net> <4fcd20dd$0$9519$9b4e6d93@newsspool1.arcor-online.net> <1tr1nuc1xy9mp$.d5s1fz9vuczz.dlg@40tude.net> <4fcdc605$0$9524$9b4e6d93@newsspool1.arcor-online.net> <1ch26v7folac1$.1gc355i72r55j.dlg@40tude.net> <4fcdf97f$0$9521$9b4e6d93@newsspool1.arcor-online.net> NNTP-Posting-Host: 96.2.54.122 Mime-Version: 1.0 X-Trace: posting.google.com 1338955757 28646 127.0.0.1 (6 Jun 2012 04:09:17 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 6 Jun 2012 04:09:17 +0000 (UTC) In-Reply-To: <4fcdf97f$0$9521$9b4e6d93@newsspool1.arcor-online.net> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=96.2.54.122; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC User-Agent: G2/1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: 2012-06-05T21:09:17-07:00 List-Id: On Tuesday, June 5, 2012 7:20:14 AM UTC-5, Georg Bauhaus wrote: > On 05.06.12 11:06, Dmitry A. Kazakov wrote: >=20 > >> (All I see is subsequences of 2#bbbb_bbbb#. For the AI part, > >> I am told to produce the most likely information that the > >> originator might have intended to send.) > >=20 > > Bad design. Don't do that. >=20 > How is producing the most likely information from a piece > of data bad design? And who am I to say "I don't do that"? PHP gives a good answer [by illustrating the wrong way to do it]. "*PHP is built to keep chugging along at all costs. __When faced with eithe= r doing something nonsensical or aborting with an error, it will do somethi= ng nonsensical.__ Anything is better than nothing. *Weak typing (i.e., silent automatic conversion between strings/numbers/et = al) is so complex that __whatever minor programmer effort is saved is by no= means worth it__." From: http://me.veekun.com/blog/2012/04/09/php-a-fractal-of-bad-design/ "And if you are in the business of creating or using magic then make it ver= y clear what it expects where and when and why and where. Be as upfront as = you possibly can and give proper warnings when something goes awry." From: http://www.pelshoff.com/2012/04/in-favour-of-typing What you're asking with the "producing the most likely information" questio= n is exactly summed up in the emphasized portions of the first quote. The s= econd quote {being more about the internal codebase, but still applicable} = could easily be rephrased "give a warning about behavior based on questiona= ble assumptions".