Only allocate a copy of style strings if requested. #441
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.
do_free_src_and_alloc_copy wasn't being checked for the placement
position, the initial map command, the title format, and the icon title
format.
Fixes #430.
I took a different approach to fixing 21 byte memory leak in merge_styles (3 tiny leaks of 7 bytes) #430. This pull request fixes 21 byte memory leak in merge_styles (3 tiny leaks of 7 bytes) #430 by only allocating a copy of the style strings if copying was requested (i.e.
do_free_src_and_alloc_copy
is True), instead of the Fix a 21 byte memory leak. #431 approach that involved trying to free the style, which broke setting icon images.I hope this PR doesn't break anything like my previous one did.
Screenshots (if applicable)
PR acceptance criteria (reminder only, please delete once read)
Your commit message(s) are descriptive. See:
https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
[https://raw.githubusercontent.com/fvwmorg/fvwm3/master/doc/README]Documentation updated (where appropriate)
Style guide followed (try and match the surrounding code where possible)
All tests are passing: although this is automatic, Codacy will often
highlight additional considerations which will need to be addressed before
the PR can be merged.
Issue number(s)
If this PR addresses any issues, please ensure the appropriate commit
message(s) contains:
at the end of your commit message, where
XXX
should be replaced with therelevant issue number.
If there is more than one issue fixed then use: