--
---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposal...@isocpp.org.
To post to this group, send email to std-pr...@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.
This raises ownership issues. Having a native handle accessor works for the thread components because once control has left the thread components' code, the threat components' no longer need complete control over the object. That isn't true for streams though, which typically do some of their own buffering. You would need to define some sort of semantics whereby accessing the native handle would be well defined.You also would need to mandate that the C++ streams be implemented directly such that there was a 1:1 native handle relationship, which may not be the case. For instance, a valid implementation of C++ iostreams would be on top of cstdio, which would not have any kind of native handle to expose.