From: Olaf Lenz <olenz@TechFak.Uni-Bielefeld.DE>
To: gsl-discuss@sources.redhat.com
Cc: Olaf Lenz <olenz@TechFak.Uni-Bielefeld.DE>
Subject: C++-Wrapper for GSL?
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <20010706181809.E23159@metropolitan.TechFak.Uni-Bielefeld.DE> (raw)
Hello again!
As I have seen when browsing the mailing lists archive, there seem to
be some others out there that would be interested or are already
working on some C++-classes that wrap the GSL.
Until now I wrote some wrapper around the Histograms and the Random
Number Generators that I would readily share with others.
Is there any interest on the side of the GSL authors to include
wrapping C++ classes into the GSL in the long or short term? Or would
it be better to build an own 'GSL++' package?
Anyway, if the answer is positive, I would be ready to contribute.
--
Cheers
Olaf
Email to olenz@TechFak.uni-bielefeld.de ***** PGP encrypted and signed
Email to: pgp-public-keys@keys.pgp.net ************** mail is welcome.
subject: get olenz@TechFak.uni-bielefeld.de for public key. **********
next reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 Olaf Lenz [this message]
2001-12-19 13:20 ` Brian Gough
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=20010706181809.E23159@metropolitan.TechFak.Uni-Bielefeld.DE \
--to=olenz@techfak.uni-bielefeld.de \
--cc=gsl-discuss@sources.redhat.com \
/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).