[vsipl++] [patch] Distributed transpose

[Jules Bergmann]

> * We need to address the many header interdependencies, in particular 
> between the serial and the parallel set. There is some circularity that 
> is very hard to break out of.

I completely agree.

Was there a particular dependency between the parallel/serial headers? 
Unfortunately the spec has a circular definition where maps return the 
processor set in a Vector, but Vectors have blocks, and blocks have 
maps, and maps have processor sets ... well you get the idea.

> 
> * There are sets of templates that form a self-contained block of 
> functionality that I think is important to document, both, from a low 
> level as well as middel-level view. I'm in particular thinking of the 
> Combine_return_type logic (which I have run across multiple times this 
> week already)

I completely agree too.

I'll take an action to add some documentation for Combine_return_type.

You'll notice I did add some gratuitous documentation to one of 
Subset_map_decl's functors ;)  Let's take this opportunity as we get 
back into the library (relearning what we've written before but didn't 
document), to add some documentation.

				-- Jules

-- 
Jules Bergmann
CodeSourcery
jules at codesourcery.com
(650) 331-3385 x705