From: Tuomo Keskitalo <Tuomo.Keskitalo@iki.fi>
To: Gerard Jungman <jungman@lanl.gov>
Cc: gsl-discuss@sourceware.org
Subject: Re: some general questions
Date: Sat, 10 Oct 2009 14:45:00 -0000 [thread overview]
Message-ID: <4AD09E04.60001@iki.fi> (raw)
In-Reply-To: <1254861292.28192.239.camel@manticore.lanl.gov>
Hello,
your ideas seem quite promising, I look forward to see your code. :-)
On 10/06/2009 11:34 PM, Gerard Jungman wrote:
>>> Q6. More a statement than a question: We should be more explicit
>>> about the levelization of the design. This means expressing
>>> the dependence of components clearly. For example, matrix
...
> I don't think this is a problem for machine solution. It's up to
> us to decide how the thing is organized. What depends on what,
> which parts are foundational, and which parts are built on
> top of those? Then we should organize the code so it
> expresses that.
I run a few ad hoc shell commands described below, to find the
interdependencies within current GSL directories. Even though the
results are probably not complete nor fully correct, this might provide
a starting point for the organization?
-----
Lowest level ("many" dependencies): blas, block, cblas, complex, vector,
err, ieee_utils
Intermediate level (at least one other directory seems to use these):
eigen, histogram, integration, linalg, min, permutation, poly, randist,
rng, roots, sort, statistics
Highest level (no other directory seems to use these): bspline, cdf,
cheb, combination, const, deriv, dht, diff, fit, fft, interpolation,
monte, multifit, multimin, multiroots, ntuple, ode-initval, qrng, siman,
specfunc, sum, wavelet
-----
I got to this result by running the following commands with zsh in
gsl-1.13 root directory, and by ogling the resulting
gsl-dependencies.txt file.
for f in `find -type d`; do; for g in `grep include $f/*.h $f/*.c`; do;
echo "$f : $g" >> out; done; done;
grep ': <' <out | sort | uniq | egrep -v 'doc/examples' >
gsl-dependencies-all.txt
for f in `find -type d | perl -pe 's/\.\///' | sort`; do; echo "$f is
used by:" >> gsl-dependencies.txt; grep $f gsl-dependencies-all.txt |
egrep -v "^\.\/$f" >> gsl-dependencies.txt; echo ""
>>gsl-dependencies.txt; done;
--
Tuomo.Keskitalo@iki.fi
http://iki.fi/tuomo.keskitalo
next prev parent reply other threads:[~2009-10-10 14:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 10:12 containers tentative design summary Gerard Jungman
2009-10-05 14:50 ` James Bergstra
2009-10-05 23:00 ` Gerard Jungman
2009-10-05 23:45 ` James Bergstra
2009-10-06 19:59 ` Gerard Jungman
[not found] ` <645d17210910060537s762d6323pfd2bec8590ad28e9@mail.gmail.com>
2009-10-06 20:02 ` Gerard Jungman
2009-10-23 21:28 ` Brian Gough
2009-10-27 23:06 ` Gerard Jungman
[not found] ` <7f1eaee30910271628h70785125m68e47c7a7b5c25b7@mail.gmail.com>
2009-10-27 23:49 ` Gerard Jungman
2009-10-29 18:06 ` Brian Gough
2009-10-29 20:41 ` Gerard Jungman
2009-10-29 21:40 ` James Bergstra
2009-10-30 16:54 ` Brian Gough
2009-10-30 16:54 ` Brian Gough
2009-10-05 23:04 ` some general questions Gerard Jungman
2009-10-06 16:21 ` Brian Gough
2009-10-06 20:32 ` Gerard Jungman
2009-10-10 14:45 ` Tuomo Keskitalo [this message]
2009-10-24 11:16 ` Brian Gough
2009-10-14 20:00 ` Brian Gough
2009-10-15 18:39 ` Tuomo Keskitalo
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=4AD09E04.60001@iki.fi \
--to=tuomo.keskitalo@iki.fi \
--cc=gsl-discuss@sourceware.org \
--cc=jungman@lanl.gov \
/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).