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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.67.1.10 with SMTP id bc10mr23764496pad.25.1418638658787; Mon, 15 Dec 2014 02:17:38 -0800 (PST) X-Received: by 10.140.109.9 with SMTP id k9mr14642qgf.17.1418638658739; Mon, 15 Dec 2014 02:17:38 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!news.glorb.com!h15no10623018igd.0!news-out.google.com!r1ni50qat.1!nntp.google.com!w8no7944820qac.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 15 Dec 2014 02:17:38 -0800 (PST) In-Reply-To: <10b43460-09db-4fb1-9a68-4555ce57811b@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=197.86.169.17; posting-account=r0RePAgAAABkc8iAou09Mtfbf-fnKQql NNTP-Posting-Host: 197.86.169.17 References: <1a2fea61-bcc1-43a9-b6e3-edf474308402@googlegroups.com> <10b43460-09db-4fb1-9a68-4555ce57811b@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Ada Connections to this Crypto. From: mrvmurray@gmail.com Injection-Date: Mon, 15 Dec 2014 10:17:38 +0000 Content-Type: text/plain; charset=ISO-8859-1 Xref: news.eternal-september.org comp.lang.ada:23996 Date: 2014-12-15T02:17:38-08:00 List-Id: On Monday, 15 December 2014 11:30:56 UTC+2, Austin Obyrne wrote: > I am more interested in your take on using Sequential_IO (being advocated > to me) instead of my preferred Text_IO which is totally adequate as it stands. Sequential_IO can read and write ANY file and ANY data trivially. MP3s, photographs, files whose contents are otherwise opaque - ANYTHING. That includes the data that text_io can read. Text_IO can only read/write human readable _text_ files. That makes it inadequate. > What really puzzles me is the inference that using sequential_IO for which >I would have to create crypto instances has extra *cryptographic properties > that will enable any data type to be be encrypted. No. Currently, you read a text character, and turn it into a number in the range 32..126, which corresponds to its ASCII numeric value. Reading using sequential_io will give you this same 32..126 for any ASCII characters that happen to be in the sequential stream without having to go through an explicit conversion step, PLUS, you get the full 0..255 range of which 32..126 is a subset. There is no need to "create crypto instances has extra *cryptographic properties that will enable any data type to be be encrypted" at all. > I would be grateful for your opinion on this because a number of > people seem to be mixing up the CS with the Crypto. CS, mathematics and crypto are already mixed. Show your gratitude by believing this. M --