On 26 May 2001 12:40:36 GMT, cglur@onwe.co.za wrote:
>cglur@onwe.co.za wrote:
>
>"Graham Higgins" <gjh@bel-epa.com> wrote:
>> At a guess (google, given 'gsl' returns) ,,,
>>
>> GSL -- The GNU Scientific Library. ... gsl is free software. It is distributed
(snip)
>
>OK, Good.
Having the GNU library available can only be a Good Thing, but ...
>Presumably 'senior member(s)' have judged that the cost/benefit says
>do-it.
Do what?
>What skill set do we need ?
For what?
I can't spare any time to help, so I ask only out of curiosity. If it
was explained what was intended, I'm sorry I missed it - could someone
point me at the post which explained it (the news server I use seems
to have comp.lang.pop back at least as far as January).
But what, exactly, is required? This is a genuine question; it is not
obvious what is *required*[1] beyond copying documentation, and
including it and the library with the Poplog distribution.
The next level up would be to prepare a set of pop11 lib
files which included the necessary declarations for run-time
loading of the GSL functions, and possibly linking them into a
poplog image. Or would it?
And after that, then what?
I may be being naive here, particularly since I know nothing about
the problems the poplog development team had in interfacing to
the X Window System. But X is an Abomination, and is Not Nice (as
a collection of code). I defy anyone to claim otherwise.
Presumably GSL is not an Abomination. (If it is, why would we want
to use it?)
Oh, and does GSL include code for solving LP problems (Linear
Programming - a class of optimisation problems)? If so,
then I WANT it! :-). (Amongst a million other things :-).
Jonathan
[1] Jonathan's desiderata scale goes: "required", "wanted",
"desirable", "piffling about" ...
--
Jonathan L Cunningham
|