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-Thread: 109fba,cd8ed9115942852f X-Google-NewGroupId: yes X-Google-Thread: 103376,b92b95c9b5585075 X-Google-NewGroupId: yes X-Google-Attributes: gid4f1905883f,gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news2.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!feedme.ziplink.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Bill Findlay Newsgroups: comp.lang.c++,comp.lang.ada Subject: Re: Why use C++? Date: Tue, 16 Aug 2011 15:51:29 +0100 Message-ID: References: <1fd0cc9b-859d-428e-b68a-11e34de84225@gz10g2000vbb.googlegroups.com> <9ag33sFmuaU1@mid.individual.net> <1d8wyhvpcmpkd.ggiui9vebmtl.dlg@40tude.net> <150vz10ihvb5a.1lysmewa1muz4$.dlg@40tude.net> <1q4c610mmuxn7$.1k6s78wa0r8fj.dlg@40tude.net> <1vn800hbyx8k4$.1lsveclj56197$.dlg@40tude.net> <1gu6ni1yb54k3$.4nbvfqqndl8m$.dlg@40tude.net> <4e4a4534$0$7629$9b4e6d93@newsspool1.arcor-online.net> <17sfxzivd6ba0.1lpjrmelcfuoa$.dlg@40tude.net> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Trace: individual.net g+T+gl0eMn5uIwhMB29y9Q5VUS6yF3pQUSmg8+3uyBDTa+Icjg Cancel-Lock: sha1:rKGUaCXrgoqJDwB/SMM8pmjV2m4= User-Agent: Microsoft-Entourage/12.28.0.101117 Thread-Topic: Why use C++? Thread-Index: AcxcI/rn4H3lrTYKTU+QPVoIlLQNRw== Xref: g2news2.google.com comp.lang.c++:92827 comp.lang.ada:21621 Date: 2011-08-16T15:51:29+01:00 List-Id: On 16/08/2011 11:58, in article 17sfxzivd6ba0.1lpjrmelcfuoa$.dlg@40tude.net, "Dmitry A. Kazakov" wrote: > On Tue, 16 Aug 2011 12:23:48 +0200, Georg Bauhaus wrote: > >> Is changing only the representation of types, not the types, >> necessarily premature optimization? > > The answer depends on the time the change is made. "Premature" in its > original meaning (Knuth) means: during design, before functional > requirements are met. There are important cases in which the representation of types is an essential part of the functional requirement. For example, writing a bit-accurate emulator for an existing computer architecture; or processing data generated by a legacy non-Ada system. These cases are not the most common, but they are also not the ignorable trivia you claim them to be. -- Bill Findlay with blueyonder.co.uk; use surname & forename;