Fixed slight memory leak in sf::Font #1216
Closed
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.
Nothing much, but apparently it's all i'm good at 馃槥 ( see #509 )
There is also an inconsistency in the coding style; Either adding objects to the class as soon as they're created so that cleanup() frees them eventually, as is the case with the stroker object, which is cleaner IMO. Or adding them at the very end and having to clean every single one whenever there's an error loading, as it's the case with original code, this frees memory instantly but irrelevant if there's no errors (most of the time).
But I did not touch that.