From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20150622090534.GA21054@localhost> References: <20150622090534.GA21054@localhost> Date: Mon, 22 Jun 2015 11:10:04 +0100 Message-ID: From: Charles Forsyth To: Oleg , Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=089e0160aa483f113a0519187ad8 Subject: Re: [9fans] enc64() vs dec64() Topicbox-Message-UUID: 5a387e58-ead9-11e9-9d60-3106f5b1d025 --089e0160aa483f113a0519187ad8 Content-Type: text/plain; charset=UTF-8 On 22 June 2015 at 10:05, Oleg wrote: > May be a stupid question. enc64() returns a null terminated string. But > dec64() > not doing the same. What is the reason for it? > enc: binary -> string dec: string -> binary binary is just an array of bytes, and there isn't a special terminating value --089e0160aa483f113a0519187ad8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 22 June 2015 at 10:05, Oleg <lego12239@yandex.ru> wrote= :
May be a stupid question. enc64() returns a null terminat= ed string. But dec64()
not doing the same. What is the reason for it?

= enc: binary -> string
dec: string -> = binary

binary is just an array of bytes, and there isn't a special terminatin= g value
--089e0160aa483f113a0519187ad8--