dukeleto.factor tag:leto.net,2008-04-19:/factor//7 2008-11-13T07:00:23Z [ t ] [ dukeleto ] unit-test Movable Type Open Source 4.1 New blog for my Factor ramblings tag:leto.net,2008:/factor//7.118 2008-11-13T06:15:34Z 2008-11-13T07:00:23Z I have split off a new blog so that I can concentrate my concatenative nerdiness into one area and enhance it's effect. I have been hacking on the GSL bindings to Factor, specifically the Special Functions. What can I say,... Jonathan Leto Bessel functions are like sirens that sing me to shipwreck...

 I finally have some tests which use the gsl_sf_result structure. Now I need to make the API more Factorish.

  • internally checking the return status and throwing an exception with the proper stringified error message
  • make the user oblivious to the gsl_sf_result struct and return value and error to the data stack
Any other suggestions?
]]> Running a Factor Script tag:leto.net,2008:/x//1.98 2008-11-06T15:32:56Z 2008-11-06T16:18:33Z For those who are put off by the interactive UI part of Factor, you can run a script from the command-line like so#! /Users/leto/git/factor/factor  -scriptUSING: gsl gsl.sf.result gsl.sf.bessel gsl.sf.log kernel tools.test ;"gsl.sf" testNote the space after the ! is necessary... Jonathan Leto
#! /Users/leto/git/factor/factor  -script

USING: gsl gsl.sf.result gsl.sf.bessel gsl.sf.log kernel tools.test ;

"gsl.sf" test

Note the space after the ! is necessary because every "word" in Factor must be separated by a space. The practice of running factor as a non-interactive script is not encouraged, but in certain  situations it wins the day. The above script could be factored to take an argument of a subsystem to test and then I would make a key-binding in vim (or emacs or whatever) so that when I am editing a file and I type ,t it shows me the results of that subsystems tests.

All of this stuff can be done in the interactive UI, but I think people will fiddle with Factor more  if they can easily bolt it onto their current workflow. People tend not to even try things that require totally changing their current tool chain. For me, I am editing the source of the GSL bindings in VIM, so having that script is invaluable. I hack on the source and whenever I change anything important I run the tests by hitting 2 keys. It is really important to make running and writing tests as easy as possible, or they won't get written at all. 

Today ...... is a good day to hack.

]]> GSL for Factor tag:leto.net,2008:/x//1.93 2008-11-01T14:15:41Z 2008-11-13T07:08:31Z Factor is a new language that is gaining momentum in the open source community. A few of the core members were in town visiting after the creator Slava gave a Google Tech Talk. Over beers and pizza at the Lucky Lab... Jonathan Leto Factor is a new language that is gaining momentum in the open source community. A few of the core members were in town visiting after the creator Slava gave a Google Tech Talk. Over beers and pizza at the Lucky Lab NW the Factor guys told me how FFI works and we had a binding to a Bessel function working within half an hour. It's that frickin' easy! 

Here is the gitweb for factor-gsl, which currently has support for all Bessel functions. 

To clone master repo:

git clone http://leto.net/code/factor.git

Example usage: 

( scratchpad ) USE: gsl.sf.bessel
( scratchpad ) 10 gsl_sf_bessel_J0 .
-0.2459357644513484

There are tests also, but the docs are still a bit rough. 
]]>