Re: [Log4cpp-devel] Updating for C++17 and 20

[<log...@li...>]

Hello, Jeff.

throw(..) specifications with the list inside are removed already, please
checkout current master branch.

In order to move project towards c++20, throw() should be removed or
preferably replaced with noexcept.
auto_ptr can also be replaced with unique_ptr ancestor, small code
adjustments are required.

However, there is the following  consequence of these changes: the project
will stop being compilable on the older platforms with outdated compilers
which I see an undesirable effect.

If folks around do not mind, we may try to move the project there. Or,
alternatively, think about probable solution including preprocessor's code
adjustment for both pre- and post- c++11 compilers.

Alex.

вс, 10 нояб. 2019, 2:06 <log...@li...>:

> Hi - is log4cpp pretty much dead, or, just stable I guess. Well, parts
> won't compile under a C++ 17 - conforming compiler, not even when used as
> binaries (ie, even the headers are wrong) and for C++20 they're entirely
> forbidden:
>
>
> https://stackoverflow.com/questions/47727108/are-dynamic-exception-specifications-invalid-in-c17#47727338
>
> The code compiles under 17 just fine if you simply remove all of the
> throw([...]) specifications, I can submit a pull request for that I guess.
> But we / someone should also get rid of the auto_ptr<>s. I thought of
> replacing them with unique_ptr<>s, but I'm afraid of subtle bugs due to
> possible different semantics. Any experts feel like taking that on?
>
> Jeff
>
>
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel
>