Displaying 2 results from an estimated 2 matches for "e96c5aa859f8".
2013 Aug 25
0
libopusfile's memory management.
...ther way I can think
> of to resolve this issue is to provide a tags duplication function: ie
> opus_tags_copy(OpusTags *_dst,const OpusTags *src) and other duplication
> functions for other structures as well (for the sake of completeness.)
Added in https://git.xiph.org/?p=opusfile.git;h=e96c5aa859f8;a=commitdiff
I'm holding off on adding copy routines for the other structures with
internal allocations for now, since they are generally not mutable, and
the application has better control over the lifetime. But let me know if
you wind up needing one.
2013 Aug 25
3
libopusfile's memory management.
Would it be possible to include a re-export of the malloc, calloc, realloc,
and free being used by opus file's implementation of OpusTags handling?
This might seem redundant or ridiculous but I'm having difficulty getting
the right versions that my compiler allows that's compatible with
libopusfile. In the debugger I can see that the memory location that my
malloc is returning is