From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31290 invoked by alias); 21 Sep 2009 12:08:06 -0000 Received: (qmail 31268 invoked by uid 22791); 21 Sep 2009 12:08:05 -0000 X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_50,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.network-theory.co.uk (HELO mail.network-theory.co.uk) (66.199.228.187) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 21 Sep 2009 12:08:02 +0000 Date: Mon, 21 Sep 2009 12:08:00 -0000 Message-ID: From: Brian Gough To: Tuomo Keskitalo Cc: GSL Discuss Mailing List Subject: Re: GSL 2.0 roadmap (one man's view) In-Reply-To: <4AB5F77F.8020104@iki.fi> 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> <4AB5F77F.8020104@iki.fi> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.2 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Message-Mac: 7979f184699a3d8c141e0af84cccb5e6 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/msg00062.txt.bz2 At Sun, 20 Sep 2009 12:35:59 +0300, Tuomo Keskitalo wrote: > 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? The block type corresponds to the C++ valarray class (the gsl_block struct members are the same as those in C++ valarrays). The idea was that it would simplify interoperability with C++. -- Brian Gough