From: Gerard Jungman <jungman@lanl.gov>
To: GSL discussion list <gsl-discuss@sourceware.cygnus.com>
Subject: Re: gsl Development Query
Date: Fri, 01 Sep 2000 13:32:00 -0000 [thread overview]
Message-ID: <39B0131C.EC4F5BA9@lanl.gov> (raw)
In-Reply-To: <39AEE8CC.C7EE3BB8@netwood.net>
"E. Robert Tisdale" wrote:
>
> The FFT object (what you call a gsl_fft_wavetable_complex) is OK.
> But then you go on to itemize the private members:
>
> typedef struct {
> size_t n;
> size_t nf;
> size_t factor[64];
> gsl_complex *twiddle[64];
> gsl_complex *trig;
> double *scratch;
> } gsl_fft_wavetable_complex;
>
> Why did you do this?
> It isn't necessary for the application programmer
> to have any of this information.
Look, we can all sit and play C++ compiler. But there's
no point. The implementation language for this project
does not make a distinction, and nobody at this end is
going to make pedantic distinctions. People who use C
libraries have to apply some common sense. That is a
fact (unfortunate perhaps) of the language.
And he did it because it was useful to write it
down somewhere. Don't quibble about where he wrote
it down.
> I think that you've painted yourself into a corner
> and you will be obliged to support this particular
> data representation and the implied algorithm forever.
Nobody is painting any corners, and nobody is
obliged to do anything. Chill out.
--
G. Jungman
next prev parent reply other threads:[~2000-09-01 13:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-31 17:25 E. Robert Tisdale
2000-09-01 13:32 ` Gerard Jungman [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-04 13:10 E. Robert Tisdale
2000-09-04 13:00 E. Robert Tisdale
2000-09-04 12:38 E. Robert Tisdale
2000-09-04 13:00 ` Steve ROBBINS
2000-09-03 17:34 E. Robert Tisdale
2000-09-03 16:20 E. Robert Tisdale
2000-09-03 17:22 ` Randall Judd
2000-09-04 11:45 ` Brian Gough
2000-09-02 16:31 E. Robert Tisdale
2000-09-04 11:39 ` Steve ROBBINS
2000-09-02 9:22 E. Robert Tisdale
2000-09-01 18:58 E. Robert Tisdale
2000-09-02 0:12 ` Eleftherios Gkioulekas
2000-09-02 15:12 ` Gerard Jungman
2000-09-01 15:18 E. Robert Tisdale
2000-09-01 14:26 E. Robert Tisdale
2000-08-31 21:37 E. Robert Tisdale
2000-09-01 13:33 ` Gerard Jungman
2000-08-30 16:18 E. Robert Tisdale
2000-08-31 12:28 ` Brian Gough
2000-08-25 3:34 PPC Linux Bugs, and a perplexing problem F J Franklin
2000-08-30 6:07 ` gsl Development Query F J Franklin
2000-08-30 8:15 ` Thomas Walter
2000-08-30 10:46 ` Brian Gough
2000-08-30 12:10 ` Gerard Jungman
2000-08-31 12:28 ` Brian Gough
2000-08-31 14:38 ` Gerard Jungman
2000-08-31 15:53 ` Randall Judd
2000-09-01 14:53 ` Gerard Jungman
2000-09-01 16:46 ` Randall Judd
2000-09-02 14:56 ` Gerard Jungman
2000-09-03 14:29 ` Randall Judd
2000-09-04 11:45 ` Brian Gough
2000-09-04 14:27 ` Randall Judd
2000-08-31 16:15 ` 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=39B0131C.EC4F5BA9@lanl.gov \
--to=jungman@lanl.gov \
--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).