Daniel Russel wrote: > Given the shift to modules, it is not clear that the original include > directory structure is the best any more (with IMP/restraints holding > restraints, for example). I would propose that all public classes/ > functions in the modules API be in headers in the module main include > directory.
Sure, why not? It doesn't really make a whole lot of difference either way - the only reason to have a non-flat directory structure is to make things easier to look at with 'ls' (the structure has no influence on the way modules are linked).
Ben