From: Oleg <lego12239@yandex.ru>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] enc64() vs dec64()
Date: Mon, 22 Jun 2015 13:30:17 +0300 [thread overview]
Message-ID: <20150622103017.GA9687@localhost> (raw)
In-Reply-To: <CAOw7k5jrTpAf=PEHcTH53Pv9kCYVJaBjPfV_s38LcjDdbpDMRw@mail.gmail.com>
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:
>
> > 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
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!
--
Неманов Олег (Nemanov Oleg)
prev parent reply other threads:[~2015-06-22 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 9:05 Oleg
2015-06-22 10:10 ` Charles Forsyth
2015-06-22 10:30 ` Oleg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150622103017.GA9687@localhost \
--to=lego12239@yandex.ru \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).