Thanks again Dan, I enjoyed reading Rob Pike's blog post. I think you are right with your point, it has to be one way and not every machine use the same representation anyway.
Cheers, Pablo On Wed, Jan 11, 2017 at 7:32 PM, Dan Kortschak < [email protected]> wrote: > On Wed, 2017-01-11 at 16:46 +1100, Pablo Rozas Larraondo wrote: > > Thanks Dan. I'm just surprised that Gray16 uses big endian when, for > > example, Go's uint16 type uses the little endian convention. > > On *most* supported architectures. > > > I guess I find this weird and I want to know if there is a reason for > > implementing Gray16 this way. > > It has to be one way. > > You might like to see this article for thinking about it. > https://commandcenter.blogspot.com.au/2012/04/byte-order-fallacy.html > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
