Search found 6 matches
- Sat Nov 30, 2013 6:23 am
- Forum: newLISP in the real world
- Topic: curl bindings for newLISP
- Replies: 1
- Views: 2217
Re: curl bindings for newLISP
Good work. Thanks a lot.
- Tue Dec 18, 2012 4:46 am
- Forum: newLISP in the real world
- Topic: newLISP compute matrix with lapacke and some problems
- Replies: 5
- Views: 2685
Re: newLISP compute matrix with lapacke and some problems
Thank you, lutz. I transform "a" to float explicitly: (set 'af (map float a)) then, the LAPACK_dgels works well. "pack" looks like malloc or other allocate memory functions in C. It allocates continuous memory and assigns value of some type (float, int etc) to every position. This is so-called "pack...
- Mon Dec 17, 2012 6:12 pm
- Forum: newLISP in the real world
- Topic: newLISP compute matrix with lapacke and some problems
- Replies: 5
- Views: 2685
Re: newLISP compute matrix with lapacke and some problems
I think "char" or "int" doesn't matter, when I change "int" to/from "char", the result is the same as before. And, when I do as you said, replace (address aptr) with aptr, strangely, the result doesn't change. But when I test C array API with my own function below, the result is good. Here is code: ...
- Mon Dec 17, 2012 6:44 am
- Forum: newLISP in the real world
- Topic: newLISP compute matrix with lapacke and some problems
- Replies: 5
- Views: 2685
newLISP compute matrix with lapacke and some problems
I want to compute a matrix with lapacke. The example is here http://www.netlib.org/lapack/lapacke.html#_calling_tt_dgels_tt here is my code: (set 'LAPACKE "/usr/local/lib/liblapacke.so") (import LAPACKE "LAPACKE_dgels" "int" "int" "char" "int" "int" "int" "void*" "int" "void*" "int") (set 'a '(1 1 1...
- Sun Dec 09, 2012 1:56 pm
- Forum: newLISP in the real world
- Topic: about return value from gsl
- Replies: 3
- Views: 2050
Re: about return value from gsl
thank you lutz, it does work.
- Sat Dec 08, 2012 5:47 pm
- Forum: newLISP in the real world
- Topic: about return value from gsl
- Replies: 3
- Views: 2050
about return value from gsl
I want to do some scientific computing with gsl. but encounter some error. below is my code > (import LIB "gsl_complex_rect" "void*" "double" "double") gsl_complex_rect@7FBAD0403FD0 > (unpack "lf lf" (gsl_complex_rect 2.0 3.0)) Segmentation fault (core dumped) the complex defined in gsl like this: t...