Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The member std::fpos::seekpos() is non-Standard #44

Closed
ghost opened this issue Dec 17, 2018 · 3 comments
Closed

The member std::fpos::seekpos() is non-Standard #44

ghost opened this issue Dec 17, 2018 · 3 comments

Comments

@ghost
Copy link

ghost commented Dec 17, 2018

When I want to debug and build my project it gives me this error:
Severity Code Description Project File Line Suppression State
Error C4996 'std::fpos<_Mbstatet>::seekpos': warning STL4019: The member std::fpos::seekpos() is non-Standard, and is preserved only for compatibility with workarounds for old versions of Visual C++. It will be removed in a future release, and in this release always returns 0. Please use standards-conforming mechanisms to manipulate fpos, such as conversions to and from streamoff, or an integral type, instead. If you are receiving this message while compiling Boost.IOStreams, a fix has been submitted upstream to make Boost use standards-conforming mechanisms, as it does for other compilers. You can define _SILENCE_FPOS_SEEKPOS_DEPRECATION_WARNING to acknowledge that you have received this warning, or define _REMOVE_FPOS_SEEKPOS to remove std::fpos::seekpos entirely.

@code-affinity
Copy link

I am not involved with fixing this issue, but I have been keeping track of it because it is a big problem for me. Here's what I know: The pull request that fixes this problem is boostorg/iostreams#57. My understanding is that it has been incorporated into Boost 1.69. boostorg/iostreams#57 (comment)

@chcg
Copy link

chcg commented Feb 4, 2019

@sergey-shandar https://www.boost.org/users/history/version_1_69_0.html is available. Are you planning a release?

@sergey-shandar
Copy link
Owner

@chcg yes, I plan to release 1.69 this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants