On 10/22/2015 11:28 PM, Tinglin Liu wrote: > 2) The key and value are stored separately for each key-value pair. 'keys' > atom stores the key name table, while 'ilst' atom stores the values > corresponding to the indices in the key table. And since they are stored in > two different atoms, I have to store the name and count of the keys in the > MOVContext, and use them when parsing 'ilst'.
Right. For some reason I thought it was begin exported. It's clear to me now. >>> + union av_intfloat32 val; >>> + val.i = avio_rb32(pb); >> >> I'm not entirely sure of the portability of this code. Would this not fail >> on >> any system without IEEE floats? Still not sure about this, but I see such stuff used elsewhere in avformat, via av_int2float, so I guess we probably don't care. Someone correct me if I am mistaken. - Derek _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
