Why the imit of 16 in mxfwrap/split?
Page 1 of 1

Author:  diddek [ Fri Mar 12, 2010 9:44 am ]
Post subject:  Why the imit of 16 in mxfwrap/split?


If I go through the code of for instance mxfwrap.cpp, I find a limit of 16 here and there.

Arrays for instance, are initialized with 16:

char InFilename[16][128];

(and there are more, for instance filehandles or timecodecomponents)

Is there a particular reason for this, or is it an arbitrary limit and I could make it bigger - or even runtime determined?

Best, Dirk

Author:  Matt Beard [ Mon Mar 15, 2010 9:01 am ]
Post subject: 

The limit is simply arbitrary.

These programs are intended to be examples that show what is possible, and give developers code to experiment with, rather than fully-featured applications.

Page 1 of 1 All times are UTC
Powered by phpBB® Forum Software © phpBB Group