Experimental class in baloo

David Edmundson david at davidedmundson.co.uk
Wed Mar 21 00:16:00 UTC 2018


On Tue, Mar 20, 2018 at 9:43 AM, Michael Heidelbach <ottwolt at gmail.com>
wrote:

> Hi!
>
> I've recently introduced a new class for baloo
> <https://cgit.kde.org/baloo.git/commit/?id=9de78becc06346a734279c2dc13d081dc5861624>.
> It is mainly for debugging. As it is accompanied with a command line tool
> it may be useful for users too.
>
> It is still in an experimental state and it's likely I'll wish to change
> the public interface.
>
> 1) Is it possible to mark that class as experimental for some time and
> have the allowance to chance the interface?
>

Once you've exported symbols in the same library as baloo...not really.

> 2) If so, what is the best way to communicate that?
>
If it's purely for debugging, stick it behind some optional CMake
definition so only users who explicitly enable it have the header
installed.


David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20180321/bd7a5786/attachment.html>


More information about the Kde-frameworks-devel mailing list