types - typemap rule is confusing -
according mpi 2.2 standard section 4.1: create new data type have define typemap sequence of (type, displacement) pairs. displacements are not required positive, increasing, nor distinct.
- suppose define typemap of following sequence: {(double, 0), (char,0)} not make sense, yet possible, how can standard provide flexibility?
if that's thing find confusing typemaps, you're smarter am. particular example -- c unions this; why shouldn't typemaps allow it?
Comments
Post a Comment