From: "Jochen Küpper" <kuepper.jochen@googlemail.com>
To: gsl-discuss@sourceware.org
Subject: Re: using GSL with C++ (was Re: gsl container designs)
Date: Wed, 09 Dec 2009 21:14:00 -0000 [thread overview]
Message-ID: <61933AD2-91BE-4FE9-87B2-BC793231A148@googlemail.com> (raw)
In-Reply-To: <4B20105C.3080501@fnal.gov>
On 09.12.2009, at 22:02, James Amundson wrote:
> On 12/04/2009 12:36 PM, Brian Gough wrote:
>>
>> 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?
C++ and sometimes Python (here I more often use scipy than pygsl)
next prev parent reply other threads:[~2009-12-09 21:14 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 [this message]
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
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=61933AD2-91BE-4FE9-87B2-BC793231A148@googlemail.com \
--to=kuepper.jochen@googlemail.com \
--cc=gsl-discuss@sourceware.org \
/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).