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: a07f3367d7,73cb216d191f0fef X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit X-Received: by 10.180.10.230 with SMTP id l6mr177567wib.3.1366858394923; Wed, 24 Apr 2013 19:53:14 -0700 (PDT) MIME-Version: 1.0 Path: hg5ni24023wib.1!nntp.google.com!feeder1.cambriumusenet.nl!feed.tweaknews.nl!193.141.40.65.MISMATCH!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!border2.nntp.ams2.giganews.com!border1.nntp.ams2.giganews.com!border3.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!rt.uk.eu.org!weretis.net!feeder4.news.weretis.net!nuzba.szn.dk!news.jacob-sparre.dk!munin.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Is this expected behavior or not Date: Thu, 18 Apr 2013 21:16:58 -0500 Organization: Jacob Sparre Andersen Research & Innovation Message-ID: References: <516e6a0e$0$9505$9b4e6d93@newsspool1.arcor-online.net> <516efa28$0$9518$9b4e6d93@newsspool1.arcor-online.net> NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: munin.nbi.dk 1366337825 28654 69.95.181.76 (19 Apr 2013 02:17:05 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Fri, 19 Apr 2013 02:17:05 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Date: 2013-04-18T21:16:58-05:00 List-Id: "Dmitry A. Kazakov" wrote in message news:qtagj9gwjjxn$.ljj8purwznkr.dlg@40tude.net... ... > Your concept simply does not hold. There are simple indisputable facts: > > 1. The representation of string object is irrelevant to what string is. This is clearly false, so it's pretty clear why you end up with bizarre conclusions. Specifically, the number of characters that a string object can hold (and whether that number can change, and by how much) is *indisputably* a critical part of string object semantics. This is so tightly interwined by the underlying representation (when you chose one, you pretty much chose the other) that practically it is inseparable. It's certainly true that you can have an abstract string interface that doesn't expose the representation -- that's the idea behind my Root_String'Class proposal -- and that's useful in a limited set of circumstances (mostly in read-only situations, which is the majority of string operations anyway). But it does not describe the complete semantics of a string object, nor could it. > 2. It is impossible to have one implementation suitable for all string > objects and all application domains that use strings, e.g. DNA sequencing, > pattern matching, text processing, compiler construction etc. Of course. So what? That's why we want a variety of string types for different jobs. That gives no reason why anyone should be mixing them! What do you get when you concatenate a DNA sequence and an Ada identifier? A bug! :-) Randy.