Large programming project in SISC almost finished

Hi,

I want to show you what I have been using SISC for lately:

http://www.notam02.no/hurtigmikser/DasApplet.html

(which is an applet requiring jvm>=1.5, the programs final home is going 
to be at http://www.musikkverksted.no, but the guys at 
www.musikkverksted.no haven't got everything to work quite yet).



The applet/program is a special kind of composition program which is going
to be used in music education in Norway, age 9 and up or something
like that. It might look a little bit like a toy, but its not, and its
also possible to make high quality music with it.

Almost all of the graphics and gui is made directly in SISC, while the
signal processing is programmed using Java. The source is GPL, placed
here: http://www.notam02.no/arkiv/src/hurtigmikser_23.8.2007.tar.gz



My experience using SISC for a larger programming task (~18000 lines):

* SISC is very stable, complete, and does not give you unpleasant 
  surprises.
* Interaction with java works fine. I made some functions to make it
  more convenient though. (java.scm)
* SISC interprets code more than fast enough for common GUI/graphics 
  operations.
* Debugging usually does not work, and I am not able to reproduce when it 
  works and when it doesn't. It might seem like the 
  chance of backtracing to fail increases with the size of the program.
* Creating .scc files from the .scm files can take forever, sometimes 
  up to a minute for relatively small files, dependent on how complicated 
  the code inside the files are.

The two last points have been major causes of frustration for me, and I
hope the developers of SISC have the time to look at those. Especially the
time it takes to compile files are just horrible. In many programming
sessions, I have spent most of my time waiting for SISC to be finished
compiling the files. But all in all, I am happy with the choice of using
SISC. Although its not unlikely that it would have taken less time to do
everything directly in Java (because of the debugging problems and all the
time it takes to compile files), programming in Java isn't very much fun,
while programming in scheme is. :-) So thank you very much for this
almost excellent scheme interpreter.

Kjetil.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/