LispWorks 6.0 Personal Edition is out ...
lispworks.com
lispworks.com
I bought Linux, Windows, and Mac LispWorks professional licenses about 8 or 9 years ago. One very nice thing about LispWorks is that the utility to make standalone applications has a "tree shaker" to toss unused code so executables can be reasonably small (compared to SBCL where a standalone app is about 30 MB minimm or Clozure CL where a standalone app is around 20MB minimum).
I always thought that the tree shaker was the really big win for LispWorks.
Now, when I want to use a Lisp to create small standalone applications I use Gambit-C Scheme.
BTW, about 10 years ago, I was paid a fee to work on the LispWorks documentation - but that does not bias my opinion.
I remember Actor (an Algol-ish syntax flavor of Smalltalk that ran on Windows 3) had a similar thing to trim the image file prior to packing up the runtime. It removed everything that whatever your app was didn't depend on.
Why the heck did Symantec buy the whitewater group if they were just going to kill the damn thing!
We use a proprietary Prolog interpreter (SICStus), but it comes with very good support and it has some advantages over open source interpreters that matter to us. Plus they provide continuing support/maintenance for their previous major version.
The free SBCL and Clozure CL systems are very good also, and free support from the developers can be good: one customer project using SBCL 4 years ago hit a snag running on a 64 GB server and one of the developers sent me a patch in a few hours. Excellent!
There are also explicit paging APIs which allow you to unmap ranges and later map them back in, but it's a pain. Usefulness of this is limited anyway, as physical RAM is limited to around 3GB on the client versions of Windows (Windows Server supports more via PAE).
A useful trick is to run a 32-bit process on a 64-bit version of Windows, you can get close to 4GB of address space that way. No need for special boot flags.
For all of these cases, your executable needs a special "big address space" flag set.
FWIW, most x86 Linux kernels set aside 3GB for user space.
Seems a pretty fair segmentation to me.
hmm, Lisp or C++.
I see they are listing it as one of their success stories: http://www.lispworks.com/success-stories/netfonds-primetrade...