-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
Compilation Hints #4
Comments
There are multiple different kinds of checksum. In TCP alone you have two different types fro IPv4 and IPv6. What is a good syntax to select between them?
I don't think the replace syntax is necessarily a good idea. Not every check is 16-bits like TCP/IP. |
I've thought about this for far too long, and I've come to a conclusion. The goal of |
New plan. Here are the headers, required by every Every file is required to have a bit ordering identifier and a byte ordering identifier. It'll be at the top of the file, the first line, after a tilda. You may specify them in either order. The valid keywords are:
The byte ordering is currently only used for multi-byte characters in string literals. You may then turn padding on and it will use the bit ordering you specified. It MUST appear directly after the header and would look like this:
|
Change-Of-New Plan:
but this is not:
|
closed in 767b44a |
When going form hext to binary, there are some things that are too important to leave as command line flags. Stuff like the bitness (#3) and maybe even, if it's implemented, the checksum location (#2).
Here's how I think it should be done here. Not many hints, and they should be short. Here are all the ones I can think might be needed:
Where
~padding off
is the default value.The text was updated successfully, but these errors were encountered: