Re: Ada Connections to this Crypto.

[mrvmurray@gmail.com]

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
--