Hi, Dan! >> I find "const" correctness a very useful concept. I guess that users > > It is on road map for the C++ interface what it's worth > https://www.mltframework.org/changes/todo/
Oops... I am so sorry! I think I checked on Shotcut's roadmap, instead. If there is a concern, I am already very happy! :-) > You will see that the developers of MLT are also the developers of Shotcut > [...] Yes, I saw that! You are all awesome! :-) I started writing this suggestion in https://forum.shotcut.org/. But then I realized that probably the right place to suggest this would be on the MLT mailing list. > If we add some const-ness, I think it requires a major SONAME change > since it changes the method signatures in mlt++.vers - our compiler symbol > versioning file. I see. Maybe, this could be done slowly in a different branch. Then, it could be merged later, on the next "major release". I don't know the proper way to implement this const-ness thing. If it is to be done through new typedefs, like typedef const mlt_producer_s* mlt_producer_const; Then, it could be temporarily defined without the "const"! Like this... :-) typedef mlt_producer_s* mlt_producer_const; Or, maybe, with a "#define": (I don't really know if this is correct... it has been more than 15 years without programing in C/C++) #ifdef USE_CONST_CORRECTNESS #define CONST_CORRECTNESS const #else #define CONST_CORRECTNESS #endif [...] typedef CONST_CORRECTNESS mlt_producer_s* mlt_producer_const; André Caldas. PS: Notice that I am not asking for the MLT team to implement anything. I just want to know your opinions and if maybe I can help! :-) _______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
