Support for Secure De-allocation of memory #437
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
cdunn2001
force-pushed
the
JSONCPP_STRING
branch
from
2cf743c to
1f73267
Compare
|
Let's move the discussion to #442. |
cdunn2001
force-pushed
the
JSONCPP_STRING
branch
4 times, most recently
from
0ded628 to
ae56465
Compare
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.
This squashes the previous branch of secure allocator to a single commit and then merges JSONCPP_STRING in and finally fixes up any changes (essentially Json::String -> JSONCPP_STRING).