From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6474 invoked by alias); 20 Sep 2009 09:36:08 -0000 Received: (qmail 6464 invoked by uid 22791); 20 Sep 2009 09:36:07 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_50 X-Spam-Check-By: sourceware.org Received: from smtp4.welho.com (HELO smtp4.welho.com) (213.243.153.38) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 20 Sep 2009 09:36:03 +0000 Received: from [10.0.0.133] (cs181229105.pp.htv.fi [82.181.229.105]) by smtp4.welho.com (Postfix) with ESMTP id 8741A5BC037 for ; Sun, 20 Sep 2009 12:35:59 +0300 (EEST) Message-ID: <4AB5F77F.8020104@iki.fi> Date: Sun, 20 Sep 2009 09:36:00 -0000 From: Tuomo Keskitalo User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090707) MIME-Version: 1.0 To: GSL Discuss Mailing List Subject: Re: GSL 2.0 roadmap (one man's view) References: <48E25CA9.6080306@iki.fi> <490DE4BD.7070907@iki.fi> <497B00F6.2080400@iki.fi> <498727E5.6080407@iki.fi> <49AA9DB5.6030908@iki.fi> <49FB01D1.30000@iki.fi> <4A7ADFDC.9080408@iki.fi> <1251414774.23092.80.camel@manticore.lanl.gov> <1251414939.23092.82.camel@manticore.lanl.gov> <1253062087.23092.965.camel@manticore.lanl.gov> In-Reply-To: <1253062087.23092.965.camel@manticore.lanl.gov> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gsl-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gsl-discuss-owner@sourceware.org X-SW-Source: 2009-q3/txt/msg00057.txt.bz2 On 09/16/2009 03:48 AM, Gerard Jungman wrote: > In the end, everybody's data structures amount to something plastered > over the top of double *, with some meta-information for layout and > life-cycle control. This includes things likes the row-major vs > column-major distinction, which we should not ignore any longer. > > But this rapidly turns into a discussion of gsl_vector and friends, > which we should save for later. Data structures are sort of foundational, shouldn't we discuss them also now? I'd like to know how the developers of GSL ended up using gsl_block within gsl_vector and gsl_matrix. Why is it needed? tda in gsl_matrix struct is a bit of a mystery to me, what is it used for? I agree that use of other libraries and even other languages with GSL should be made as easy as possible. Data structures with dimension > 1 should be explicit about the data being stored as "column-major" or "row-major". -- Tuomo.Keskitalo@iki.fi http://iki.fi/tuomo.keskitalo