Hi, I’m wondering how should error checking be done when it comes to using mlt++. Is there some standard way to do that?
Example, which motivates the question: If I do something like that „Mlt::Profile profile;” in my C++ code, it theoretically declares and initializes a valid mlt_profile object. But looking further, it contains „mlt_profile_init(NULL);” call which can return NULL if internal calloc() fails. Which would mean that profile would not be a valid object, as „instance” member would be NULL, and any setters called will do a NULL pointer dereference… It is written in „docs/mlt++.txt” that objects may not be valid and they contain „is_valid()” method to check their validity before they’re used. But, for example, it seems Profile doesn’t have such a function… So, it seems, I need to check by hand if Profile’s instance is not NULL before using a Profile object… But to know that, I needed to go as deep as „mlt_profile_init()” declaration. I wonder then, is there is some less involved, standard way to do error checking? (So I wouldn’t need to read MLT code every time I use an object, to know what can go wrong). Best, Paweł ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
