On Tue, Oct 26, 2021 at 8:04 AM Andre Caldas <andre.em.cal...@gmail.com> wrote:
> It would be very nice, IMO, if functions like > "mlt_producer_get_length(mlt_producer self)" were declared in such a > way that "self" points to a "const". > > 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/ But we have not got around to it due to lack of concern, priorities, and/or business. You will see that the developers of MLT are also the developers of Shotcut and Kdenlive, and there are not many of us. 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. > of the MLT library that care for const correctness would benefit. > > https://isocpp.org/wiki/faq/const-correctness > > Of course, since MLT is already non-const correct, making it so could > be a nightmare and break things. But simple access methods that do not > return references should be okay to change. The pointers typedefs in > "mlt_types.h" makes things a little harder, though. :-( > > I think libraries should always be "const-correct", because otherwise > the library imposes its "non-const-correctness" to their users. It > affects most the users of the library, more then the library itself. > > This is just a suggestion. Most people probably don't really mind. > Feel free to just ignore this e-mail. :-) > > And sorry if this has already been discussed. =o) > > > André Caldas. > > > _______________________________________________ > Mlt-devel mailing list > Mlt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mlt-devel >
_______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
