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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8a2a8de919fd29da X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-03-31 20:11:28 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!arclight.uoregon.edu!wn13feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!sccrnsc01.POSTED!not-for-mail Message-ID: <3E89119E.4040002@attbi.com> From: "Robert I. Eachus" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: PL/I outflanks Fortran References: <2Q_ca.1611$dE2.3935@newsfeeds.bigpond.com> <64050551.0303180643.7901fb94@posting.google.com> <3e77364f$0$24810$91cee783@newsreader02.highway.telekom.at> <3E78B30E.7C37E27E@adaworks.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit NNTP-Posting-Host: 24.62.164.137 X-Complaints-To: abuse@attbi.com X-Trace: sccrnsc01 1049170283 24.62.164.137 (Tue, 01 Apr 2003 04:11:23 GMT) NNTP-Posting-Date: Tue, 01 Apr 2003 04:11:23 GMT Organization: AT&T Broadband Date: Tue, 01 Apr 2003 04:11:23 GMT Xref: archiver1.google.com comp.lang.ada:35844 Date: 2003-04-01T04:11:23+00:00 List-Id: > i'm not sure it matters whether i find it useful, after all you find only 4 > out of 15 to be useful. i.e., that there is little common use for e.g base > 9 did not prevent the language designers from providing for it, so why not > the entire well defined range? There is a subtle place where it matters, Ada.Text_IO.Integer_IO.Get reads a number (without a point) according to the syntax of an integer literal. (Ada.Text_IO.Float_IO allows a point.) This means that when reading a string like 23#ABCEDFGHI... the read will stop immediately after the F. So as long as we are allowing A, B, C, D, E, and F for hexadecimal constants, there is no reason to outlaw bases lower than 16, but higher bases would have noticable effects even if a user never expected to use based numbers.