Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I believe <strong>Common Lisp</strong> should suit your needs. I always have some code in my SLIME/Emacs session that wouldn't compile. You can always tweak things, redefine functions in run-time. It is actually very good for prototyping.</p> <p>A few years ago it took me quite a while to learn. But nowadays we have quicklisp and everything is so much easier.</p> <p>Here I describe my development environment: <a href="https://stackoverflow.com/questions/6546834/install-lisp-on-my-linux-machine/6548692#6548692">Install lisp on my linux machine</a></p> <p>PS: I want to give an example, where Common Lisp was useful for me: Up to maybe 2004 I used to write small programs in C (the keep it simple Unix way).</p> <p>The last 3 years I had to get lots of different hardware running. Motorized stages, scientific cameras, IO cards.</p> <p>The cameras turned out to be quite annoying. Usually you have to cool them down to -50 degree celsius or so and (in some SDKs) they don't like it when you close them. But this is exactly how my C development cycle worked: write (30s), compile (1s), run (0.1s), repeat.</p> <p>Eventually I decided to just use Common Lisp. Often it is straight forward to define the foreign function interfaces to talk to the SDKs and I can do this without ever leaving the running Lisp image. I start the editor in the morning define the open-device function, to talk to the device and after 3 hours I have enough of the functions implemented to set gain, temperature, region of interest and obtain the video.</p> <p>Then I can often put the SDK manual away and just use the camera.</p> <p>I used the same interactive programming approach when I have to parse some webpage or some weird XML. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload