public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Thierry Moisan" <thierry.moisan@gmail.com>
To: "Brian Gough" <bjg@gnu.org>
Cc: gsl-discuss@sourceware.org
Subject: Re: gsl_matrix_complex functions documentation
Date: Mon, 23 Jun 2008 01:43:00 -0000	[thread overview]
Message-ID: <55577cf0806221843p5e1cba6atae5bfd5f1e527894@mail.gmail.com> (raw)
In-Reply-To: <87hcblkwhr.wl%bjg@network-theory.co.uk>

Hello,

I thought the gsl_matrix_complex part may need a bit more explanation
without being described separately for each functions. At first I
thought the gsl_matrix_complex_set function was used in a way we could
enter directly the complex value instead of using the gsl_vector
functions. Something like gsl_matrix_complex_set(gsl_matrix * m,
size_t i, size_t j, double x, double y) where x and y are the
cartesian components of the complex number x + i y. But I see it would
mean you would have to create 3 functions for the same usage : one for
rect, one for polar and one to enter directly an already existing
gsl_vector.

So finally I don't think you should change anything. It was simply me
who was wrong. If you wish to add more documentation on that go ahead
but I think that if I had read a bit more I would have got it.

Thanks for the fast reply!

Thierry Moisan

2008/6/22 Brian Gough <bjg@gnu.org>:
> At Sun, 22 Jun 2008 15:19:19 -0400,
> Thierry Moisan wrote:
>> Hi, I'm the student who work on Math::GSL for google summer of code.
>> The goal of Math::GSL is to port the GSL library to Perl. While
>> working on this project, I realized the gsl_matrix_complex functions
>> haven't been documented yet. I wanted to know if it was meant to be
>> done soon. If not, I thought I could help by documenting them. I'll
>> have to document them anyway inside my project, so I tought it would
>> be better not to duplicate the work.
>>
>> I'd like to know how I could work on the development of the
>> documentation? To who or which server/repository do I have to push my
>> changes?
>
> Hello,
>
> The individual description of each function is given only for the
> 'double' version of the functions.  The others (including complex,
> char, int, etc) have the same form so they aren't described
> separately.
>
> The introduction to the chapter gives a full list of the valid types.
> If there are any specific functions that you think need to be
> described separately let me know.  Thanks.
>
> --
> Brian Gough
>
> p.s. If you need the repository for any other reason the details are
> at http://www.gnu.org/software/gsl/
>
>

      reply	other threads:[~2008-06-23  1:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-22 19:19 Thierry Moisan
2008-06-22 21:09 ` Brian Gough
2008-06-23  1:43   ` Thierry Moisan [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=55577cf0806221843p5e1cba6atae5bfd5f1e527894@mail.gmail.com \
    --to=thierry.moisan@gmail.com \
    --cc=bjg@gnu.org \
    --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).