Displaying 2 results from an estimated 2 matches for "opus_tags_copi".
Did you mean:
opus_tags_copy
2013 Aug 25
0
libopusfile's memory management.
alpha thinktink wrote:
> On Sat, Aug 24, 2013 at 7:56 PM, Timothy B. Terriberry
> <tterribe at xiph.org <mailto:tterribe at xiph.org>> wrote:
>
> alpha thinktink wrote:
> > is returning in tags handlers. So of course when I call
> opus_tags_clear
> > or any other tags modification routine on an OpusTags struct with
> > contents
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