[Gsll-devel] extra info in the example section
Hey, I have a suggestion that might be obvious for all experts but nonetheless a little help for newbies like myself. Especially since gsll might be the first lisp package they (like me) want to try out. In the example section in the web page, would it be possible to add a small "getting started". Maybe it can be combined with the first example. For example. Getting started Make sure that your are able to load the system. (asdf:operate 'asdf:load-op :gsll) This should load up the system without errors. The last lines should be looking something like: ; registering #<SYSTEM GRID {1003EC1961}> as GRID ; loading system definition from /usr/share/common-lisp/systems/c-array.asd ; into #<PACKAGE "ASDF0"> ; registering #<SYSTEM C-ARRAY {1002D0F471}> as C-ARRAY NIL * Then make sure that you use the gsll package, run the following (in-package :gsl) This should tell you that the gsll package is ready with the following line: #<PACKAGE "GSLL"> Now you are ready to try out one of the many gsl functions (jacobian-elliptic-functions 0.2d0 0.81d0) which should give you something like this: 0.19762082367187703d0 0.9802785369736752d0 0.9840560289645665d0 If the above steps have worked successful, you are ready to jump into the amazing world of gsll.
On Tue, Apr 27, 2010 at 6:40 AM, N J <raphexion@gmail.com> wrote:
Hey,
I have a suggestion that might be obvious for all experts but nonetheless a little help for newbies like myself. Especially since gsll might be the first lisp package they (like me) want to try out.
In the example section in the web page, would it be possible to add a small "getting started". Maybe it can be combined with the first example. For example.
stuff deleted... Good idea. Here is another one that would be useful even for the pros. A gsll-probe, that would probe the system to make sure that gsll is loadable. The main thing that comes to mind, and that can look scary to a newbie is if the gsl libraries are not loadable. Along those lines, I was wandering if the gsll setup would be easier if the user were required to set-up a feature *gsll-user* (or some other such name. This symbol would have in its plist the gsl library location. Mirko
I'm not sure what you're looking for here, but I've never had "GSL libraries not loadable" (not sure what you mean here; not found in the path?). Doesn't the form (cffi:use-foreign-library libgsl) at the end of init/init.lisp fail with some kind of reasonable error message if it doesn't find the libraries? What else is needed? Liam On Tue, Apr 27, 2010 at 8:56 AM, Mirko Vukovic <mirko.vukovic@gmail.com> wrote: ...
Good idea. Here is another one that would be useful even for the pros. A gsll-probe, that would probe the system to make sure that gsll is loadable. The main thing that comes to mind, and that can look scary to a newbie is if the gsl libraries are not loadable.
Along those lines, I was wandering if the gsll setup would be easier if the user were required to set-up a feature *gsll-user* (or some other such name. This symbol would have in its plist the gsl library location.
Mirko
See below: On Tue, Apr 27, 2010 at 9:22 PM, Liam Healy <lhealy@common-lisp.net> wrote:
I'm not sure what you're looking for here, but I've never had "GSL libraries not loadable" (not sure what you mean here; not found in the path?). Doesn't the form (cffi:use-foreign-library libgsl) at the end of init/init.lisp fail with some kind of reasonable error message if it doesn't find the libraries? What else is needed?
Liam
On Tue, Apr 27, 2010 at 8:56 AM, Mirko Vukovic <mirko.vukovic@gmail.com> wrote: ...
Good idea. Here is another one that would be useful even for the pros. A gsll-probe, that would probe the system to make sure that gsll is loadable. The main thing that comes to mind, and that can look scary to a newbie is if the gsl libraries are not loadable.
I was thinking of absolute Newbies who get horrified when lisp drops into a debugger. A way to deal with that might be to use exception handling with `gentler' messages. And other than finding libraries, sometimes the libraries are not loadable: with SBCL1.0.34, I got an `offset' error (don't remember exactly what), and with 1.0.37, I could not load 64-bit libraries. Anyways, I don't mean to throw this task to you. I'll think about an implementation, and if I come up with something sensible, I will post it here. Mirko
On Wed, Apr 28, 2010 at 8:17 AM, Mirko Vukovic <mirko.vukovic@gmail.com> wrote:
See below:
On Tue, Apr 27, 2010 at 9:22 PM, Liam Healy <lhealy@common-lisp.net> wrote:
I'm not sure what you're looking for here, but I've never had "GSL libraries not loadable" (not sure what you mean here; not found in the path?). Doesn't the form (cffi:use-foreign-library libgsl) at the end of init/init.lisp fail with some kind of reasonable error message if it doesn't find the libraries? What else is needed?
Liam
On Tue, Apr 27, 2010 at 8:56 AM, Mirko Vukovic <mirko.vukovic@gmail.com> wrote: ...
Good idea. Here is another one that would be useful even for the pros. A gsll-probe, that would probe the system to make sure that gsll is loadable. The main thing that comes to mind, and that can look scary to a newbie is if the gsl libraries are not loadable.
I was thinking of absolute Newbies who get horrified when lisp drops into a debugger. A way to deal with that might be to use exception handling with `gentler' messages.
That's OK, provided it can be turned off. I'm not sure there's a general way to provide a global handler in CL though.
And other than finding libraries, sometimes the libraries are not loadable: with SBCL1.0.34, I got an `offset' error (don't remember exactly what), and with 1.0.37, I could not load 64-bit libraries.
Weird. I have no idea where that comes from, and I'm using a fairly recent SBCL and I've been using 64 bit for years.
Anyways, I don't mean to throw this task to you. I'll think about an implementation, and if I come up with something sensible, I will post it here.
OK, sounds good.
Mirko
Good idea. I'll try to remember to do something like this. On Tue, Apr 27, 2010 at 6:40 AM, N J <raphexion@gmail.com> wrote:
Hey,
I have a suggestion that might be obvious for all experts but nonetheless a little help for newbies like myself. Especially since gsll might be the first lisp package they (like me) want to try out.
In the example section in the web page, would it be possible to add a small "getting started". Maybe it can be combined with the first example. For example.
Getting started
Make sure that your are able to load the system.
(asdf:operate 'asdf:load-op :gsll)
This should load up the system without errors. The last lines should be looking something like:
; registering #<SYSTEM GRID {1003EC1961}> as GRID ; loading system definition from /usr/share/common-lisp/systems/c-array.asd ; into #<PACKAGE "ASDF0"> ; registering #<SYSTEM C-ARRAY {1002D0F471}> as C-ARRAY NIL *
Then make sure that you use the gsll package, run the following
(in-package :gsl)
This should tell you that the gsll package is ready with the following line:
#<PACKAGE "GSLL">
Now you are ready to try out one of the many gsl functions
(jacobian-elliptic-functions 0.2d0 0.81d0)
which should give you something like this:
0.19762082367187703d0 0.9802785369736752d0 0.9840560289645665d0
If the above steps have worked successful, you are ready to jump into the amazing world of gsll.
_______________________________________________ Gsll-devel mailing list Gsll-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/gsll-devel
participants (3)
-
Liam Healy -
Mirko Vukovic -
N J