[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] update
- From: "Schleimer, Ben" <bensch128@xxxxxxxxx>
- Date: Wed, 10 Oct 2007 20:42:25 -0700 (PDT)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=4uF61lfXEHFJ3glvBJl2i6++jUg71NHW1e1Y8bZ1vLAWOyN7nKdvCnB5YtNECHPbeTSHkBuQ5RE/7USGtJ5zkVBlE4FSWNvNxxaD0YUr1xAxUiwlIDiq2WXHaTYDSlX0HvuGHDAzs9maQUe+I2pdhDgHR/lXgcasfSDeyvlmYPc=;
> The plan is to include in eigen2 (possibly as a separate "eigen-sparse") a
> wrapper around the sparse classes from gmm++.
> The wrapper should at least:
> - provide a nicer API than gmm++ does, for instance overloaded operators.
> - provide Qt-style copy-on-write, canceling the overhead of the overloaded
> operators returning by value; thus it'd still not be as good as expression
> templates but already quite good.
Wow, I guess this is a requirement.
> - allow mixing sparse types with other eigen2 types, and uniformize the
> API as much as possible.
Yes, that makes sense
> Regarding the last point, we should at least provide
> conversion constructors; but a nicer and more sophisticated solution would
> be to let both both dense and sparse objects inherit a common curious base
> class, so as to completely unify the API.
Humm, maybe this would be good to do for the dense classes for now and then it'll be easy to do
the same for the sparse classes later...
> I'd very much welcome help with the sparse stuff, as I'm already busy
> enough with the rest :)
I'm pretty slammed by work but If i ever get a free moment, I'll look into trying to start
wrapping the sparse gmm++ classes. (but don't count on me yet :(
Anyway, keep up the good work. I love the progress...