Add documentation for some nasl functions and use nasl_perror() on invalid input #608
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
ArnoStiefvater
force-pushed
the
packet-forgery-functions-documentation
branch
4 times, most recently
from
167647c
to
43bbf5c
Compare
ArnoStiefvater
force-pushed
the
packet-forgery-functions-documentation
branch
from
43bbf5c
to
de70fa7
Compare
jjnicola
approved these changes
Oct 20, 2020
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.
What:
Add documentation.
Use nasl_perror() instead of printf when function does not get expected/needed input.
Why:
For easy comprehension of functions and better linting of nasl plugins.
How:
Checklist: