-----Original Message----- From: Boost On Behalf Of Oliver Kowalke via Boost Sent: Thursday, December 13, 2018 9:29 AM

I don't know why defining BOOST_COROUTINES_NO_DEPRECATION_WARNING does not work for you?! But I've removed the warning (even I was told to add such a warning by the community some years ago) ...

The boost community is made up of different people with different opinions as the slack discussion shows (I thought that Vinnie had solved that problem by now anyway, but maybe I'm wrong). FYI: The only problem I have with this warning is that it is unclear what it means. I would have expected the library to be removed a few releases after this warning appears or a clear statement, that no further maintenance will happen but that doesn't seem to be the plan is it? If you just want to inform your users that there is a new version of coroutines, then a compile-time warning is imho the wrong solution Best Mike

Oliver

Am Di., 11. Dez. 2018 um 14:33 Uhr schrieb Vinnie Falco via Boost < boost@lists.boost.org>:

...

Can we please turn off this deprecation warning for now? At least when Boost.Coroutine is being included to work with Asio? I get neverending complaints from users about this warning in Beast:

https://travis-ci.org/vinniefalco/beast/jobs/466272022#L1091

I am of course defining BOOST_COROUTINES_NO_DEPRECATION_WARNING:

<

https://github.com/boostorg/beast/blob/010fb4b08c05ce82cf4a87d9985c5b4998d95...

...

...

But this warning happens when building the coroutine library not when compiling Beast's tests and examples.

Regards

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost