From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Mon, 22 Jun 2015 13:30:17 +0300
From: Oleg <lego12239@yandex.ru>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Message-ID: <20150622103017.GA9687@localhost>
References: <20150622090534.GA21054@localhost>
	<CAOw7k5jrTpAf=PEHcTH53Pv9kCYVJaBjPfV_s38LcjDdbpDMRw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAOw7k5jrTpAf=PEHcTH53Pv9kCYVJaBjPfV_s38LcjDdbpDMRw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] enc64() vs dec64()
Topicbox-Message-UUID: 5a3e0666-ead9-11e9-9d60-3106f5b1d025

On Mon, Jun 22, 2015 at 11:10:04AM +0100, Charles Forsyth wrote:
> On 22 June 2015 at 10:05, Oleg <lego12239@yandex.ru> wrote:
>=20
> > May be a stupid question. enc64() returns a null terminated string. B=
ut
> > dec64()
> > not doing the same. What is the reason for it?
> >
>=20
> enc: binary -> string
> dec: string -> binary
>=20
> binary is just an array of bytes, and there isn't a special terminating
> value

You're right. I use base64 to mask a white space symbols in strings and i
completely forgot about the main base64 purpose :-).

Thank you!

--=20
=D0=9D=D0=B5=D0=BC=D0=B0=D0=BD=D0=BE=D0=B2 =D0=9E=D0=BB=D0=B5=D0=B3 (Nema=
nov Oleg)