Should extensible implementations allow other message flags?

Open chriskohlhoff opened this issue 10 years ago • 3 comments

So users can pass through message flags not in the proposal.

Feb 26 '15 15:02 chriskohlhoff

If we require the flags to match the POSIX values, then have to include the POSIX header files, or copy the values from them. If we don't require that, (and do a translation at runtime), we will inhibit the ability of users to extend the flags with their own values.

Feb 26 '15 15:02 mclow

I have followed filesystem's lead and added tables mapping the socket_base flags to their POSIX equivalents. Applied in bf3dcfb9683e2f48e1ab30b63256913401f711f2.

Apr 11 '15 10:04 chriskohlhoff

Pre-Lenexa Summary

[socket.base]

Operating systems may provide POSIX-like message flags not included in the proposal, and in my opinion should be able to make use of them.

The change was included in revision 5. An implementation can be found on the master branch of Asio's GitHub repository.

May 04 '15 11:05 chriskohlhoff