There are two suggestions that I have before a release is made: 1. Add in more examples, the two that are there are very simple and not very helpful(I can help adding some examples, but I don't have great knowledge of how everything works together). 2. I noticed that there are only 4 c++ files that are actually compiled into the library; would it make sense to put those in the headers so that libsigc++ would become a header-only library?
-Robert Middleton On Wed, Aug 28, 2019 at 1:08 PM Kjell Ahlstedt <kjellahlst...@gmail.com> wrote: > > The plan has been to keep libsigc++-3.0 and API/ABI-breaking versions of > some other modules (e.g. glibmm) very unstable until gtk4 and gtkmm4 > become stable. I don't know when that will be. > > But I wonder if that's really necessary or desirable for libsigc++-3.0. > As far as I know, no more API/ABI-breaking changes are planned. > > Murray, what do you say? Should we release the first stable version of > libsigc++-3.0 soon, without waiting for gtk4 to become stable? > > /Kjell > > Den 2019-08-28 kl. 00:51, skrev Robert Middleton: > > > Hi all, > > > > I'm working on a library that uses libsigc++ and I've upgraded it to > > the newest libsigc++ API(it compiles at least, I don't know if it > > works). Before I do any release of my library, I would like to make > > sure that libsigc++ is at a stable version and at least somewhat > > available in distribution repos(e.g. Debian/Ubuntu). Is there any > > sort of timeframe for when this may be released? I still have a few > > months of work to do on my side, so it's not important that libsigc++ > > be released soon, I'm just trying to plan out a rough timeframe. > > > > -Robert Middleton _______________________________________________ libsigc-list mailing list libsigc-list@gnome.org https://mail.gnome.org/mailman/listinfo/libsigc-list
