On Tue, Jan 20, 2009 at 11:42:33PM +0000, [email protected] wrote: > From: David Flynn <[email protected]> > > > Signed-off-by: David Flynn <[email protected]> > --- > schroedinger/schrodecoder.c | 73 > ++++++++++++++++++++++++++++++++++++------- > schroedinger/schrodecoder.h | 10 +++++- > schroedinger/schroencoder.c | 31 ++++++++---------- > schroedinger/schroengine.c | 30 +++++++++--------- > schroedinger/schroqueue.c | 69 +++++------------------------------------ > schroedinger/schroqueue.h | 16 ++-------- > 6 files changed, 109 insertions(+), 120 deletions(-)
I'm not a big fan of this patch, since I don't think it moves us closer to the optimal data structure for storing an array of pictures. At some point, I'd like to have a combined SchroPicture and SchroEncoderFrame, which means that SchroQueue can be renamed SchroPictureQueue and have a more picture-oriented API. So this one is a no. All others in the n/10 series are yes. Perhaps even a "duh, yes!" in some cases. dave... ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Schrodinger-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/schrodinger-devel
