Re: Large programming project in SISC almost finished

Hi, Kjetil



> My experience using SISC for a larger programming task (~18000 lines):
>
> * SISC is very stable, complete, and does not give you unpleasant
>   surprises.

That would fit success stories page on SISC's web-site nicely if there was  
one :)



> * 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.

It indeed seems to be a little bit slower than it could be expected. It  
would be really great if the loading speed could be increased. Even though  
I think we should be greatful to developers of SISC for what we have  
already.

But why do you need to recompile all the files, instead of only those that  
changed? Do you use macroses so extensively  that it is hard to determine  
what files were affected by changes?


It is also interesting to me how you developed your applet. Lisp, and  
scheme in particular, associates with interactive development. Did you use  
REPL on applet to develop code?


I've been looking through your code and this: (eval '(import os)) made me  
curious. Why don't you simply use (import os)?



Best regards,
  Nikita

-------------------------------------------------------------------------
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/