> That's something to consider, but please keep in mind a sense of
> perspective: Anthony measured a _negligible_ performance hit (5 * 10^-6
> seconds).
>
> Are there any real-world applications that would suffer tremendously from
> this academic slow-down?
Yes, but that is a micro-benchmark. Re
On Sat, Mar 26, 2016 at 9:55 PM, Sascha Schumann <
sascha.schum...@myrasecurity.com> wrote:
> > > PHP already offers bin2hex()/hex2bin() and
> base64_encode()/base64_decode().
> > > This covers part, but not all, of RFC 4648.
> > >
> > > I'd like to extend the coverage to include, at minimum, Base
On Sat, Mar 26, 2016 at 9:38 PM, Stanislav Malyshev
wrote:
> Hi!
>
> > PHP already offers bin2hex()/hex2bin() and
> base64_encode()/base64_decode().
> > This covers part, but not all, of RFC 4648.
> >
> > I'd like to extend the coverage to include, at minimum, Base32.
>
> What's the use case for
> > PHP already offers bin2hex()/hex2bin() and base64_encode()/base64_decode().
> > This covers part, but not all, of RFC 4648.
> >
> > I'd like to extend the coverage to include, at minimum, Base32.
>
> What's the use case for it? Is anybody using base32 now?
I'd have a few times if the functio
Hi!
> PHP already offers bin2hex()/hex2bin() and base64_encode()/base64_decode().
> This covers part, but not all, of RFC 4648.
>
> I'd like to extend the coverage to include, at minimum, Base32.
What's the use case for it? Is anybody using base32 now?
> I'd also like to make these functions to
Hi Scott,
On Wed, Mar 23, 2016 at 3:29 AM, Scott Arciszewski wrote:
> PHP already offers bin2hex()/hex2bin() and base64_encode()/base64_decode().
> This covers part, but not all, of RFC 4648.
>
> I'd like to extend the coverage to include, at minimum, Base32.
>
> I'd also like to make these funct
