Re: [eigen] nesting |
[ Thread Index | Date Index | More lists.tuxfamily.org/eigen Archives ]
It is working. Now I just have to double check all Flag definitions within Eigen, something around ~53, since potentially I need to add the EIGEN_PROPAGATE_NESTING_BIT define. I could also do a lot of testing - what do you think how much is sane? See the attached file which basically tests Replicate, Reverse, Select in combination with and without different kinds of products. I think testing every single combination is a little bit overkill - what do you think? - Hauke On Sat, Feb 6, 2010 at 12:38 PM, Hauke Heibel <hauke.heibel@xxxxxxxxxxxxxx> wrote: > It should have been "toggle only the storage order." > > Since we now have bit which are not inherited, we might rename > HereditaryBits bits and introduce a new set. How about > > DominantBits /* always inherited */ > RecessiveBits /* only in rare cases inherited */ > > Then, in the future one could do > > Flags = OtherType::Flags & ~RecessiveBits > > to disable only those we don't want to inherit. This will of course > only then make sense, when there is the possibility for new recessive > bits in the future or just because we like it... > > - Hauke >
Attachment:
nesting_test.cpp
Description: Binary data
Mail converted by MHonArc 2.6.19+ | http://listengine.tuxfamily.org/ |