[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen <eigen@xxxxxxxxxxxxxxxxxxx>
- Subject: [eigen] Std Vector again
- From: Keir Mierle <mierle@xxxxxxxxx>
- Date: Thu, 25 Jun 2009 22:01:39 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=SBVoE/daI1O4NlZRSUTfpi5epSHG89e+UaIUczJ+EkA=; b=uvMfkqZv3pQF7Hr8lpGBHuI+cvPMqlcTJJAdo03g3n1ngCMQV8PNK/DA/H5dmWcJFE r7zX/ZqNbCJFIyCx69SB3hxOTvHjgvP5hWd2sZdWpImrPSopmqH64AJ7+h0bK6fuVINT ecqMirzEs7EENY9vSyXYxtu3M6S39360gfxIE=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=KncYOoAibLMCoyNeeAks8JPsKMCcyqP18nmP9RKYqIrWBLoWeMREo9/3evWVu7g8/k lcqwOp8cB8DK3nLp9XCwGxVB7Nj/SFvu/O0SO40jkUQbnEsLbpJrRd3OaX6+cDDVPQWK BXSPM/CMSFW56h24JbHc75FwWO4tzsYYbRM/0=
I started porting libmv to eigen 2.0.3, and got many assert failures due to putting vectorized eigen types into std::vectors or structs (which went into std::vectors). Oddly enough, it worked fine before.
I first addressed this by using the eigen allocator, but this was not appealing because I had to add an extra allocator parameter all over the place. Because current C++ doesn't support templated typedefs, you are forced to put the allocator parameter everywhere if you are using templated code.
Then I tried switching to using the eigen specialization in Eigen/StdVector. That ended up being worse, because suddenly my header files had to be included in a certain order, or there would be mysterious runtime breakage. I consider it important that headers can be included in any order.
So now I'm left with a tree half-converted to 2.0.3.. I'm not sure where to go next.
What about having an Eigen::vector<> class?