On Tue, Jul 23, 2013 at 9:07 PM, Gregory Maxwell wrote:
> order to and from the wire, which is part of why the protocol is LE
> everywhere,
*before someone corrects me, it's not LE everywhere (I meant
"manywhere" :P)— there is just enough BE to keep you on your toes. :P
--
On Tue, Jul 23, 2013 at 8:54 PM, Wendell wrote:
> Forking for curiosity's sake:
> Is there a substantial barrier to endian independence in the Bitcoin codebase?
Not really. The software was originally written to write out memory
order to and from the wire, which is part of why the protocol is LE
On Wednesday, July 24, 2013 3:54:25 AM Wendell wrote:
> Is there a substantial barrier to endian independence in the Bitcoin
> codebase?
I got the obvious stuff ('endian' branch in my repo), but it still didn't work
when I moved on. I haven't had time to try to figure out why not yet.
Luke
Forking for curiosity's sake:
Is there a substantial barrier to endian independence in the Bitcoin codebase?
-wendell
grabhive.com | twitter.com/grabhive
On Jul 24, 2013, at 3:45 AM, Douglas Huff wrote:
> The fact that you're even trying to package and/or at some point have
> packaged and shi
4 matches
Mail list logo
