That's much easier: yes. On Mon, Feb 27, 2017 at 2:08 PM, Glen Newton <glen.new...@gmail.com> wrote: > Ah, I've been thinking about this issue too much and have confused myself. > > And, I have expressed it as an XY Problem! :-( > > My real question should have been: if I write a byte to a file on one > architecture, will the byte be the same on all other architectures (i.e. > 386, amd64, arm, s390x, ppc64le) if read by a Go program on them? > > Sorry for my confusion. :-) > > Thanks, > Glen > > On Monday, February 27, 2017 at 4:45:19 PM UTC-5, Glen Newton wrote: >> >> >> >> Given a byte b, how do I convert it to a byte of particular endianness? >> It is not clear to me looking at "encoding/binary" >> >> (I am assuming that golang byte endianness varies across architectures. If >> this is wrong please educate me). :-) >> >> Thanks, >> Glen > > -- > 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 golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.
-- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
