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=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Bug in Ada - Latin 1 is not a subset of UTF-8 Date: Thu, 20 Oct 2016 09:36:31 +0200 Organization: Aioe.org NNTP Server Message-ID: References: <86f0d2fe-d498-4bc4-bb9d-e34629c89bb4@googlegroups.com> NNTP-Posting-Host: vZYCW951TbFitc4GdEwQJg.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:32143 Date: 2016-10-20T09:36:31+02:00 List-Id: On 20/10/2016 02:31, Randy Brukardt wrote: > "Dmitry A. Kazakov" wrote in message > news:nu4nee$18le$1@gioia.aioe.org... > ... >> Numeric character is a constraint expressible in Ada: >> >> subtype Numeric is Character range '0'..'9'; >> >> Numeric string constraint is not expressible, but it still a constraint. > > It's expressible as a predicate, though; that's the entire point of > predicates (to act like user-defined constraints): > > subtype Numeric_String is String > with Dynamic_Predicate => (for all E of Numeric_String => E in > Numeric); > > It's not 100% as good as a constraint (as modifications of individual > components won't be checked), but it almost always will do the job. Not nice. Is there a reason why, apart from premature optimization? > You also could declare a new type with the proper constraint: > type Numeric_String is array (Positive range <>) of Numeric; > > That will have all of the string operations, but it (unfortunately) can't be > converted to String (you'd have to write a function to do that). > > Since both of these possibilities exist, I'd hardly call the constraint "not > expressible". At worst, it's inconvinient to express it. Yes, maybe. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de