public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Rhys Ulerich" <rhys.ulerich@gmail.com>
To: "Brian Gough" <bjg@network-theory.co.uk>
Cc: "Patrick Alken" <patrick.alken@colorado.edu>, gsl-discuss@sourceware.org
Subject: Re: [Help-gsl] Submitted patch to add bspline derivative capabilities
Date: Fri, 12 Dec 2008 12:19:00 -0000	[thread overview]
Message-ID: <4a00655d0812081343l75585bf1m3db904f6b48f0565@mail.gmail.com> (raw)
In-Reply-To: <m3r64iid87.wl%bjg@network-theory.co.uk>

[-- Attachment #1: Type: text/plain, Size: 598 bytes --]

Makes sense, and the edits/documentation cleanups look consistent throughout.

There a couple of lingering comments that'll be misleading to anyone
reading the bspline.c file.  One final patch, attached, will kill
those.

Thanks,
Rhys


On Mon, Dec 8, 2008 at 3:11 PM, Brian Gough <bjg@network-theory.co.uk> wrote:
> I've added this with some minor changes (I've moved the bspline
> workspace out of the derivative workspace, to avoid any confusion
> about the ownership of the memory -- so the derivative functions take
> the normal bspline workspace and a derivative workspace as arguments).
>
>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: remove-associated-workspace-co.patch --]
[-- Type: text/x-diff; name=remove-associated-workspace-co.patch, Size: 1118 bytes --]

remove associated workspace comments

From: Rhys Ulerich <rhys.ulerich@gmail.com>


---

 bspline/bspline.c |    6 ++----
 1 files changed, 2 insertions(+), 4 deletions(-)

diff --git a/bspline/bspline.c b/bspline/bspline.c
index 465943b..ab7c742 100644
--- a/bspline/bspline.c
+++ b/bspline/bspline.c
@@ -127,7 +127,7 @@ gsl_bspline_deriv_alloc()
   Allocate space for a bspline derivative workspace. The size of the
 workspace is O(2k^2)
 
-Inputs: bspline - gsl_bspline_workspace of the associated bspline
+Inputs: k      - spline order (cubic = 4)
 
 Return: pointer to workspace
 */
@@ -208,7 +208,6 @@ gsl_bspline_breakpoint (size_t i, gsl_bspline_workspace * w)
 /*
 gsl_bspline_free()
   Free a gsl_bspline_workspace.
-Any associated gsl_bspline_deriv_workspace should be freed beforehand.
 
 Inputs: w - workspace to free
 
@@ -228,9 +227,8 @@ gsl_bspline_free (gsl_bspline_workspace * w)
 /*
 gsl_bspline_deriv_free()
   Free a gsl_bspline_deriv_workspace.
-The associated gsl_bspline_workspace should be freed afterwards.
 
-Inputs: w - workspace to free
+Inputs: dw - workspace to free
 
 Return: none
 */

  reply	other threads:[~2008-12-08 21:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4a00655d0811191412t371982eev1bb77325719860f7@mail.gmail.com>
2008-11-19 23:42 ` Patrick Alken
2008-12-07 12:29   ` Brian Gough
2008-12-08 21:12     ` Patrick Alken
2008-12-08 21:43       ` Brian Gough
2008-12-09  9:15         ` Patrick Alken
     [not found]           ` <4a00655d0811291850u684d1cd8k2bab8c651045cb11@mail.gmail.com>
2008-12-09 22:58             ` Patrick Alken
2008-12-10 18:25           ` Brian Gough
2008-12-11 12:52             ` Patrick Alken
     [not found]               ` <4a00655d0812051440v46865adbsfcc10bb7dce28d98@mail.gmail.com>
2008-12-11 15:18                 ` Rhys Ulerich
2008-12-12 11:14                   ` Brian Gough
2008-12-12 12:19                     ` Rhys Ulerich [this message]
2008-12-12 17:20                       ` Brian Gough
2008-12-11 17:03               ` 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=4a00655d0812081343l75585bf1m3db904f6b48f0565@mail.gmail.com \
    --to=rhys.ulerich@gmail.com \
    --cc=bjg@network-theory.co.uk \
    --cc=gsl-discuss@sourceware.org \
    --cc=patrick.alken@colorado.edu \
    /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).