[ https://issues.apache.org/jira/browse/STDCXX-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546124 ]
Martin Sebor commented on STDCXX-563: ------------------------------------- A few things to consider: 1. The long term goal should be to eliminate the dependency of our headers on any particular implementation of the thread library and abstract everything under a common (stdcxx-only) interface. 2. Another long term goal should be to eliminate the binary incompatibility between reentrant (thread-safe) and ordinary builds. 3. In the meantime, does it make sense to introduce platform-specific subdirectories into the include directory (along the same lines as what we have under src/) or should we follow the _config.h approach taken in rev 382600 (i.e., append a suffix to the basename of the _mutex.h header)? > split up rw/_mutex.h > -------------------- > > Key: STDCXX-563 > URL: https://issues.apache.org/jira/browse/STDCXX-563 > Project: C++ Standard Library > Issue Type: Improvement > Components: Build > Affects Versions: 4.2.0 > Reporter: Martin Sebor > Fix For: 4.2.1 > > > The internal header <rw/_mutex.h> has become too big and hard to maintain. It > would be an improvement to split it up into multiple headers, one for each > supported implementation of threads, along the lines of what was done with > the <rw/_config.h> header in > http://svn.apache.org/viewvc?view=rev&revision=382600. This is too big to do > for 4.2 but simple enough that it could go in 4.2.1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.