Eventually backwards compatibility has to be broken anyway. If the Level changes, then that would be a good time to switch over to standard(std/boost) smart pointers as well, which may break other code that depends on Object. For the most part I don't think this will have a large impact on library-using code, as at least in my case I only use the LOG4CXX_level macros.
Perhaps it would be best to do a release of what currently exists before the backwards compatibility is broken? -Robert Middleton On Thu, Oct 27, 2016 at 5:50 AM, Thorsten Schöning <tschoen...@am-soft.de> wrote: > Guten Tag Peter Westman, > am Donnerstag, 27. Oktober 2016 um 11:11 schrieben Sie: > > > My suggestion is to have getInfo return a const Level& instead of a > > LevelPtr. > > But that would change the interface and "everyone" would need to change > things. On the other side, "const Level*" would at least be compatible > with the current invocation of LevelPtr on the caller side, but would > fail assignments and such as well. > > So, break back compatibility and if so, with which form? > > I don't use Levels in my codebase, so I'm fine with such a break. ;-) > Additionally I would prefer "const Level&" as well. > > Mit freundlichen Grüßen, > > Thorsten Schöning > > -- > Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de > AM-SoFT IT-Systeme http://www.AM-SoFT.de/ > > Telefon...........05151- 9468- 55 > Fax...............05151- 9468- 88 > Mobil..............0178-8 9468- 04 > > AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln > AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow > >
