From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19785 invoked by alias); 14 Oct 2008 22:41:41 -0000 Received: (qmail 19777 invoked by uid 22791); 14 Oct 2008 22:41:40 -0000 X-Spam-Check-By: sourceware.org Received: from ug-out-1314.google.com (HELO ug-out-1314.google.com) (66.249.92.171) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 14 Oct 2008 22:40:30 +0000 Received: by ug-out-1314.google.com with SMTP id m2so943923uge.39 for ; Tue, 14 Oct 2008 15:40:19 -0700 (PDT) Received: by 10.66.239.16 with SMTP id m16mr4983879ugh.9.1224024019576; Tue, 14 Oct 2008 15:40:19 -0700 (PDT) Received: from ?192.168.2.22? (e177193076.adsl.alicedsl.de [85.177.193.76]) by mx.google.com with ESMTPS id j27sm1321729ugc.7.2008.10.14.15.40.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 14 Oct 2008 15:40:18 -0700 (PDT) From: Daniel Franke To: gsl-discuss@sourceware.org Subject: Re: simplicity vs. efficiency of algorithms in GSL Date: Tue, 14 Oct 2008 22:41:00 -0000 User-Agent: KMail/1.9.9 Cc: Gerard Jungman References: <200809221621.54890.emanuele.passera@treuropa.com> <1224019738.14338.157.camel@bellerophon.lanl.gov> In-Reply-To: <1224019738.14338.157.camel@bellerophon.lanl.gov> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810150045.47237.franke.daniel@gmail.com> 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: 2008-q4/txt/msg00013.txt.bz2 On Tuesday 14 October 2008 23:28:58 Gerard Jungman wrote: > Here's the way I see it. Anybody who uses lapack already > faces this problem; if you want to use lapack, you have > to get your ducks lined up in columns at the start. [snip] > Are these problems best solved as part of a general > "interface to fortran", or are they specific to > matrix operations? Is any of this addressed in > the new fortran standard (fortran-2003 apparently > has specific standardization for inter-language > support, including stuff like passing structs > back and forth, but I don't know the details). F2003 Standard (final draft): http://www.j3-fortran.org/doc/year/04/04-007.pdf -- 8< -- 15.2.5 Interoperability of array variables" NOTE 15.18 For example, a Fortran array declared as INTEGER :: A(18, 3:7, *) is interoperable with a C array declared as int b[][5][18] -- 8< -- Does this help? Daniel