New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Using a BOM (TOM?) to communicate endianness #10

Open

todofixthis opened this issue Jan 6, 2018 · 0 comments

todofixthis commented Jan 6, 2018 •

edited

Loading

How do we distinguish between little-endian and big-endian trits?

For example, consider the following sequence of trits:

00++000++--+-_bal3

If we interpret this value as little-endian (least significant trit first), then the value is -424242₁₀.
If we interpret this value as big-endian (most significant trit first), then the value is 79022₁₀.

We have the same problem with bits, of course, which is (for example) why some UTFs use a BOM.

Should decoded trits have a similar feature (Trit Order Mark — TOM)?

todofixthis changed the title ~~Using a TOM to communicate endianness~~ Using a BOM (TOM?) to communicate endianness

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment