From: Alberto Manuel Brandao Simoes <albie@alfarrabio.di.uminho.pt>
To: GSL LIST <gsl-discuss@sourceware.cygnus.com>
Subject: Documentation
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <20011024180759.A29431@alfarrabio.di.uminho.pt> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
Hello!
As many people knows, numexp is using GSL as a source for scientific
methods. NumExp, is being a front-end to GSL, and it is normal that people
will seek documentation on NumExp for GSL methods. That's true, too, that
GSL functions wrappers change some of the arguments, and so, GSL documentation
is not very accurate for some functions.
All this, to ask for permition to retype some of GSL documentation on
numexp GSL module documentation (of course, with the source maintained.
Alberto
--
| Alberto Manuel Brandão Simões |
| albie@alfarrabio.di.uminho.pt |
| http://numexp.sourceforge.net |
next reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 Alberto Manuel Brandao Simoes [this message]
2001-12-19 13:20 ` Documentation Brian Gough
2008-08-21 17:47 Documentation Reinhold Bader
2008-08-21 19:40 ` Documentation (2) Reinhold Bader
2008-08-26 14:54 ` Documentation 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=20011024180759.A29431@alfarrabio.di.uminho.pt \
--to=albie@alfarrabio.di.uminho.pt \
--cc=gsl-discuss@sourceware.cygnus.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).