Adding a safe reference counter for initialization/deinitialization #47
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 counter is necessary, when the application makes use of
multiples libraries
each dependent oflibinstpatch
. Examples:Swami
is dependent oflibinstpatch
andfluidsynth
.fluidsynth
could be optionally dependent oflibinstpatch
. In this caselibinstpatch
is owned twice (byswami
and byfluidsynth
).fluidsynth
,libinstpatch
is only owned byfluidsynth
.libinstpatch
,libinstpatch
is only owned by this application.This counter ensures that internal
initialization
(ordeinitialization
) is done only one time.This is required because
libinstpatch
is dependent ofGObject
which doesn't accept that the sameGtype
be registered multiple times.