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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,fd8c808621763c34
X-Google-Attributes: gid103376,public
From: Simon Wright <simon@pogner.demon.co.uk>
Subject: Re: help Please
Date: 1999/01/26
Message-ID: <x7vsocyzgu2.fsf@pogner.demon.co.uk>#1/1
X-Deja-AN: 437401956
X-NNTP-Posting-Host: pogner.demon.co.uk:158.152.70.98
References: <36ab9be5.2873369@news.ptd.net> <m3u2xgwa9x.fsf@mheaney.ni.net>
X-Complaints-To: abuse@demon.net
X-Trace: news.demon.co.uk 917418052 nnrp-05:16220 NO-IDENT
 pogner.demon.co.uk:158.152.70.98
Organization: At Home
Newsgroups: comp.lang.ada
Date: 1999-01-26T00:00:00+00:00
List-Id: <comp.lang.ada>

Matthew Heaney <matthew_heaney@acm.org> writes:

> You can't "typecast" a character to integer, like this
> 
>      ... Integer (C) ...
> 
> but of course you can convert a character into its underlying integer
> representation either by using Unchecked_Conversion or Character'Pos.

I would have thought the original problem would have expected the
character '1' to act in this context as if it had the numeric value 1
(rather than 49 which Character'Pos might give you)