|Re: [eigen] Eigen "views"|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] Eigen "views"
- From: Jose Luis Blanco <joseluisblancoc@xxxxxxxxx>
- Date: Tue, 16 Aug 2011 15:48:38 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=lyGEykDg2BYGe4W7qIb4EhT1+xAChJ7y/ZfGBZTwnCw=; b=LwVJosHnt4b9S1WQ7ajm0r+XzlPJYFHkLELRMbMoAWdZK2dUBpFXr/l/9+galcFDYW aQPzUlA9Wl3nP3SscuVSYVuBVZ/sjABySSIvxmCei+f6XHoAfIzkW8ikF77zVukdcY/L 18ZU7hV3d7P/c8OG7OFZE1PjRrXWoEh2vd8FA=
I would be also quite interesting in this feature, but... shouldn't it
come at the cost of losing vectorization optimizations?
Or are the inner workings of Eigen such smart that would dynamically
build SSE "packets", etc.?
On Tue, Aug 16, 2011 at 3:10 PM, Christoph Hertzberg
> On 16.08.2011 15:07, Christoph Hertzberg wrote:
>> On 16.08.2011 08:48, Gael Guennebaud wrote:
>>> m2 = m1(indices1,indices2);
>>> m2 = m1(Eigen::All,indices2);
>>> m2 = m1(indices1,Eigen::All);
>> Yes, I think this looks as close as one can get to Matlab-syntax (not
>> that this is a requirement, but it's definitely not a bad thing).
> You could even make m1(i, indices) return a row-vector etc ...
Dr. Jose-Luis Blanco-Claraco
Dpt. Ing. Civil, Mat. y Fabric - Phone: +34 951 952435
E.T.S.I. Industriales - Despacho 2.037
Universidad de Malaga - Campus Universitario de Teatinos
29071 Malaga, Spain