Eric Lemings wrote: > > > Travis Vitek wrote: >> >... >> >> rw/_meta_other.h >> * __rw_enable_if >> * __rw_conditional >> >> What do you think of this? > >Another possibility to consider is grouping them all in a subdir >of the include/rw directory; e.g., #include <rw/meta/_cv.h>. > >I figure some C++0x components will need multiple header files >rather than one or two huge 100k files. It might make sense for >such components to add a subdir within the include/rw directory. >
You're killing me! Just when I thought this thread had died... :) The discussion up to this point has led me to believe that the best thing to do is to throw all of the internal trait implementations into a single file and then separate out traits into their own files only as necessary. I _really_ don't like this as it makes for one _very_ long [probably 2000 lines] and messy header. It feels is very 'organic' and doesn't seem very well planned out at all. As I posted previously, I'd like to gather similar traits into their own files. Martin didn't seem very keen on this idea because there was no rationale for the proposed organization. There were no clear rules as to what to name the headers and what should be included in each of them. I'd love to create a rw/meta directory for all of the traits stuff. Unfortunately this isn't a scheme that we use for any of the other implementation files, so unless we can come up with an organization policy, I'm thinking we should probably stick with what we're doing. >Brad. >
