Header work for libatcmd.a - at_command.c #20
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Knight-Ops
changed the title
|
I completed libatcmd header work in 322c99f using a combination of DWARF info extraction and manual work. Closing this. Feel free to open a new PR if you have updates to the current RE'd headers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I started some work on
libatcmd.aI have the headers set up with all the dwarf information since it seems that some of the previous DWARF parses missed some enumerations such as AT_ERROR_CODE. This should mean that code can start being rewritten with the appropriate headers. I went ahead and wrong import guards in all the headers, not sure what the formatting standard is.