public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Patrick Alken <patrick.alken@Colorado.EDU>
To: gsl-discuss@sourceware.org
Subject: Re: const gsl_vector *
Date: Tue, 19 Aug 2014 22:33:00 -0000	[thread overview]
Message-ID: <53F3D0B7.20405@colorado.edu> (raw)
In-Reply-To: <53F3164F.50508@btinternet.com>

Also, the compiler should issue warnings/errors if you try to change 
anything else in the gsl_vector container. And since gsl_vector_set is 
the preferred way to set data elements, it will certainly detect a 
problem if you try to call gsl_vector_set on a const gsl_vector*

I think the main purpose of the current design was to abstract away all 
the details of gsl_vector, so in principle the user will never need to 
directly access the variables in v or directly access v->data. In 
practice, however, sometimes it is necessary to directly use those 
parameters.

  parent reply	other threads:[~2014-08-19 22:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13  0:03 Gerard Jungman
2014-08-19  9:19 ` John D Lamb
2014-08-19 22:28   ` Patrick Alken
2014-08-20  6:37     ` John D Lamb
2014-08-19 22:33   ` Patrick Alken [this message]
2014-08-27  0:08     ` 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=53F3D0B7.20405@colorado.edu \
    --to=patrick.alken@colorado.edu \
    --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).