From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Mon, 22 Jun 2015 12:05:34 +0300
From: Oleg <lego12239@yandex.ru>
To: 9fans@9fans.net
Message-ID: <20150622090534.GA21054@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Content-Transfer-Encoding: quoted-printable
Subject: [9fans] enc64() vs dec64()
Topicbox-Message-UUID: 5a1e28d2-ead9-11e9-9d60-3106f5b1d025

  Hi, all.

May be a stupid question. enc64() returns a null terminated string. But d=
ec64()
not doing the same. What is the reason for it?

Thanks.

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



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: <CAOw7k5jrTpAf=PEHcTH53Pv9kCYVJaBjPfV_s38LcjDdbpDMRw@mail.gmail.com>
From: Charles Forsyth <charles.forsyth@gmail.com>
To: Oleg <lego12239@yandex.ru>,
	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 <lego12239@yandex.ru> 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

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On 22 June 2015 at 10:05, Oleg <span dir=3D"ltr">&lt;<a href=3D"mailto:lego=
12239@yandex.ru" target=3D"_blank">lego12239@yandex.ru</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><div id=3D":14w" class=3D"a3s" style=3D=
"overflow:hidden">May be a stupid question. enc64() returns a null terminat=
ed string. But dec64()<br>
not doing the same. What is the reason for it?</div></blockquote></div><br>=
enc: binary -&gt; string</div><div class=3D"gmail_extra">dec: string -&gt; =
binary</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"=
>binary is just an array of bytes, and there isn&#39;t a special terminatin=
g value</div></div>

--089e0160aa483f113a0519187ad8--



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)