Opened 7 years ago
Last modified 6 years ago
#11860 new Bugs
Using iostreams causes lots of messages about deprecated header template_arity_spec.hpp
| Reported by: | Owned by: | Jonathan Turkanis | |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | iostreams |
| Version: | Boost 1.60.0 | Severity: | Problem |
| Keywords: | type_traits iostreams spirit | Cc: | zeratul976@… |
Description
Using headers from iostreams or Spirit cause lots of messages like the following:
develop/extern/share/boost-1.60/include/boost/type_traits/detail/template_arity_spec.hpp:13:83: note: #pragma message: NOTE: Use of this he
ader (template_arity_spec.hpp) is deprecated
In file included from develop/extern/share/boost-1.60/include/boost/iostreams/detail/is_dereferenceable.hpp:13:0,
from develop/extern/share/boost-1.60/include/boost/iostreams/detail/resolve.hpp:26,
from develop/extern/share/boost-1.60/include/boost/iostreams/detail/push.hpp:24,
from develop/extern/share/boost-1.60/include/boost/iostreams/detail/streambuf/indirect_streambuf.hpp:31,
from develop/extern/share/boost-1.60/include/boost/iostreams/stream_buffer.hpp:22,
from develop/extern/share/boost-1.60/include/boost/iostreams/stream.hpp:21
There seems to be no way how to suppress these messages.
Change History (11)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
Indeed. As I use both spirit and iostream a lot this clutters all my builds in 1.60.
Quite unusual to see this happen in spirit... I can confirm this in gcc 4.9 & 5.3 and MSVC 14 alike.
Stephan
comment:4 by , 6 years ago
| Cc: | added |
|---|
comment:5 by , 6 years ago
This still exists in 1.61.0, so it is still the first thing a new user will see when building boost for the first time.
comment:7 by , 6 years ago
boost python triggers the same warning as well
boost/python/detail/def_helper.hpp: 9
comment:9 by , 6 years ago
Yes, this is very irritating. https://github.com/zcash/zcash/issues/1259
comment:11 by , 6 years ago
https://github.com/boostorg/iostreams/pull/24 has been merged, so presumably this will be fixed in 1.62.

I get the same complaint from e.g.: In file included boost/function_types/member_function_pointer.hpp:13:0,
and In file included from boost/function_types/is_callable_builtin.hpp:13:0,