3 ms·
I use slime and the repl that it provides. I start a project generally early in the process, and put stuff in methods there, recompiling (reloading with ,lo pr
by wglb 16y ago
I use slime and the repl that it provides. I start a project generally early in the process, and put stuff in methods there, recompiling (reloading with ,lo projectname (a slime trick)) as needed.
I also often do ESC-x with the cursor positioned in a function or top-level form to compile just that function.
All good work flows with Lisp include adding little bits of code, then executing to see how the result has changed. This leverages the beauty of lisp develpment.
There are those who do something similar with vim--adding little bits of code, perhaps in a function, then pasting that either directly or with the help of a package to the REPL.
For many of my programs, I generate an executable that is kicked off automatically, e.g., by cron. To build the executable, use 'save-lisp-and-die'.
And don't hesitate to use quicklisp at http://www.quicklisp.org http://www.quicklisp.org. There are many very useful libraries there. For example, if you need to integrate through the command line, there is the getopt library.
For unit testing, i use xlunit, but I seem to be in the minority for that. There are a handful out there. Some info here http://aperiodic.net/phil/archives/Geekery/notes-on-lisp-testing-frameworks.html http://aperiodic.net/phil/archives/Geekery/notes-on-lisp-tes... and here http://www.cliki.net/development http://www.cliki.net/development.
Now you are mentioning a pretty specific deployment cycle there. WiX will work for executable delivery in a windows environment.
Keep in mind, however that many using lisp for production keep an emacs/slime session open, generally using term, to a running production instance. This is likely to be culturally different that the environment that you are describing above.
I haven't done anything that requires a continuous integration step, as my team size is just one.