public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Gough <bjg@gnu.org>
To: Gerard Jungman <jungman@lanl.gov>
Cc: gsl-discuss@sourceware.org
Subject: Re: questions about block/vector/matrix
Date: Fri, 23 Oct 2009 21:28:00 -0000	[thread overview]
Message-ID: <m33a5ann66.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <1255983086.12024.83.camel@manticore.lanl.gov>

At Mon, 19 Oct 2009 14:11:26 -0600,
Gerard Jungman wrote:
At Mon, 19 Oct 2009 14:11:26 -0600,
Gerard Jungman wrote:
> It is worth mentioning at this point that std::valarray is a
> recognized failure. The implementations could never live up
> to the intentions. See many discussions on the web, including
> an admission from the designer of valarray that it is a
> failure. It is best not to invoke valarray as a
> justification for any design choice; 

Yes, gsl_block was written in 1999, so I am just describing the reason
it was done like that at the time.  

While it's not essential, I don't think it's a bad principle to have
wrapper around malloc.

> This does not address the point, which is that the name of a
> function like gsl_vector_alloc_from_vector() is inappropriate,
> since it is not clear what is being "alloced".

That is an old undocumented function, not intended for actual use as
far as I'm aware.  Ideally it should have been removed.  The header
files no doubt contain bits of old junk.

The best description of the vectors and matrices is in the manual,
where I've written what should be the clearest description of how they
are meant to be used and some simple examples of the view functions.

The challenge for any scheme is getting reasonable const behavior in
C.  If that problem can be solved better then everything else follows
more easily.

      reply	other threads:[~2009-10-23 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05 10:12 Gerard Jungman
2009-10-16 20:12 ` Brian Gough
2009-10-19 21:37   ` Gerard Jungman
2009-10-23 21:28     ` Brian Gough [this message]

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=m33a5ann66.wl%bjg@network-theory.co.uk \
    --to=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).