<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 21.03.2018 01:16, David Edmundson
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAGeFrHDZE4PmHNSOVyLxz-jCkGCS+oBmeGhL4EJZ311QmzjVZw@mail.gmail.com">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Tue, Mar 20, 2018 at 9:43 AM,
            Michael Heidelbach <span dir="ltr"><<a
                href="mailto:ottwolt@gmail.com" target="_blank"
                moz-do-not-send="true">ottwolt@gmail.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF">
                <p>Hi!</p>
                <p>I've recently introduced <a
href="https://cgit.kde.org/baloo.git/commit/?id=9de78becc06346a734279c2dc13d081dc5861624"
                    target="_blank" moz-do-not-send="true">a new class
                    for baloo</a>. It is mainly for debugging. As it is
                  accompanied with a command line tool it may be useful
                  for users too.<br>
                </p>
                <p>It is still in an experimental state and it's likely
                  I'll wish to change the public interface.</p>
                <p>1) Is it possible to mark that class as experimental
                  for some time and have the allowance to chance the
                  interface?</p>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>Once you've exported symbols in the same library as
              baloo...not really.<br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF">
                <p>2) If so, what is the best way to communicate that?</p>
              </div>
            </blockquote>
            <div>If it's purely for debugging, stick it behind some
              optional CMake definition so only users who explicitly
              enable it have the header installed. <br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>David<br>
            </div>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    Thank you for your reply, David.<br>
    In this case I would like to hide it (and the command line tool) at
    least until 5.46.<br>
    I'm not very knowledgeable with CMake. I guess sticking it 'behind
    some optional CMake definition' will also account for it not being
    part of the library. I've never done this before can you some help
    or an example please.<br>
    <br>
    Michael<br>
    <br>
    <p><br>
    </p>
  </body>
</html>