public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Christos Siopis <siopis@umich.edu>
To: gsl-discuss@sources.redhat.com
Subject: Re: About coordinated efforts on scientific software.
Date: Tue, 22 Oct 2002 20:49:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0210221936200.7192-100000@orb.astro.lsa.umich.edu> (raw)

On Tue, 22 Oct 2002, JJ Gomez-Cadenas wrote:

> Let me bring an important subject to the discussion, that of
> wrappers. If GSL is going to be truly the core of free-software
> numerical calculations, wrappers are needed. For HEP it seems
> one would like C++ and python wrappers. I have played for more
> than a year now with a C++ wrapper for GSL and a number of
> non-trivial issues emerge, such as the speed, correct use of
> error handling, minimizing of copying of structures and the
> like, which often end up by suggesting re-implementation rather
> than wrapping (at least for some parts of the library). It would
> be nice to understand better and to discuss all those issues.

Interesting issues, indeed! Some of our very own GSL developers have
thought about some of them, see e.g.:

http://t8web.lanl.gov/people/jungman/except.pdf

My little personal experience with this is that there is a dichotomy
between "big project" folks and "Joe Numeric" folks.

If you talk to people involved with the development and maintenance of big
codes, they will probably propose some elegant top-bottom design, which
usually requires an object-oriented programming methodology to implement
and, increasingly, component programming. These folks will also often
insist that any code bigger than a hundred lines needs to follow a similar
path :) and that "a project rarely starts with the intention to become
big" but in the end, it does, so better plan early on.

If you talk to Joe Numeric, he'll wonder why you need anything else but
Fortran, he'll tell you how annoyed he is by NAG's requirement to return
error numbers, and will reprogram a new single-variable equation solver
each time he needs one because he hates black boxes :)

Seriously though, i wonder if your experience with C++ wrapping ultimately
means that we are doomed to reprogram our libraries every time we move
from one language family to another (at least if we want to do a good
job)...

Christos

             reply	other threads:[~2002-10-22 23:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 20:49 Christos Siopis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-21 11:32 Alan Aspuru-Guzik
2002-10-22  1:32 ` Manoj Warrier
2002-10-22  2:26   ` JJ Gomez-Cadenas
2002-10-22  3:02     ` Wartan Hachaturow
2002-10-22 16:33     ` Brian Gough
2002-10-22 16:55   ` Christos Siopis
2002-10-23 13:43     ` Alan Aspuru-Guzik
2002-11-05 11:36 ` JJ Gomez-Cadenas
2002-11-06  7:36   ` 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=Pine.LNX.4.44.0210221936200.7192-100000@orb.astro.lsa.umich.edu \
    --to=siopis@umich.edu \
    --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).