From: "Robert G. Brown" <rgb@phy.duke.edu>
To: James Amundson <amundson@fnal.gov>
Cc: gsl-discuss@sourceware.org, Brian Gough <bjg@gnu.org>,
Gerard Jungman <jungman@lanl.gov>
Subject: Re: using GSL with C++ (was Re: gsl container designs)
Date: Thu, 10 Dec 2009 13:42:00 -0000 [thread overview]
Message-ID: <alpine.LFD.2.00.0912100838010.3053@lilith> (raw)
In-Reply-To: <4B20105C.3080501@fnal.gov>
On Wed, 9 Dec 2009, James Amundson wrote:
> On 12/04/2009 12:36 PM, Brian Gough wrote:
>> At Tue, 24 Nov 2009 17:54:46 -0700,
>> Gerard Jungman wrote:
>>
>>> Here are header files for a couple different approaches to containers.
>> Regarding the introductory points.
>>
>> 2a+b) While we may have had some kind of goal of supporting C++ I
>> don't think it's worth encouraging that today as the gap between the
>> languages has widened so much since the start of the project.
>>
>
> I, for one, use GSL almost exclusively from C++. When I'm not using C++, I am
> usually using Python. How are other readers of this list using GSL? Are you
> using a pure C environment, or do you use C++ and/or other languages?
>
> I have no interest in debating the relative merits of various languages; I am
> just curious to know what is happening in practice.
I use C only. Consequently I come down in favor of using casts to type
e.g. generalized tensor forms, because pointer-based indirection can
lead to reasonably efficient, highly readable code (and because the GSL
really needs a generalized tensor form -- the computational universe of
interest to many scientists is not just one or two dimensional,
rectangular, with indices starting at 0 or 1.
rgb
Robert G. Brown http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb@phy.duke.edu
next prev parent reply other threads:[~2009-12-10 13:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 0:55 gsl container designs Gerard Jungman
2009-11-29 21:04 ` Brian Gough
2009-12-04 18:48 ` Brian Gough
2009-12-09 21:04 ` using GSL with C++ (was Re: gsl container designs) James Amundson
2009-12-09 21:14 ` Jochen Küpper
2009-12-09 21:54 ` Jari Häkkinen
2009-12-10 11:46 ` Brian Gough
2009-12-10 12:09 ` Brian Gough
2009-12-10 13:42 ` Robert G. Brown [this message]
2009-12-10 21:44 ` James Bergstra
2009-12-10 15:15 ` Kevin H. Hobbs
2010-01-06 11:45 ` gsl container designs Tuomo Keskitalo
2010-01-06 15:47 ` Robert G. Brown
2010-01-07 1:50 ` Gerard Jungman
2010-01-07 3:29 ` Robert G. Brown
[not found] ` <4a00655d1001062110m139c0a8tf2eae7de67da8f6f@mail.gmail.com>
2010-01-07 5:46 ` Rhys Ulerich
2010-01-07 13:22 ` Robert G. Brown
2010-01-08 20:08 ` Gerard Jungman
2010-01-07 18:29 ` Brian Gough
2010-01-06 12:04 ` Tuomo Keskitalo
2010-01-06 19:57 ` Gerard Jungman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.00.0912100838010.3053@lilith \
--to=rgb@phy.duke.edu \
--cc=amundson@fnal.gov \
--cc=bjg@gnu.org \
--cc=gsl-discuss@sourceware.org \
--cc=jungman@lanl.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).