>>27
It's usually not much code, and this is not true of all modern lisps. Writing the GC and image load/save in C is common, but it's hardly a problem to write that in asm or Lisp, if you wish to do that. Personally, I have little to no problem with this, as I never had a problem with using C for low/mid-level code (which involves a lot of pointer use), if the majority of that code was of that nature. It's not that these things couldn't be written in Lisp in the first place, just that it tends to be less effort to write the low-level OS-specific parts in C first (having to implement all the OS-specific stuff in Lisp would increase your code-base). Also, this C code is hardly a lot of code: in SBCL on Win32, sbcl.exe is 96kb (gc, some glue code and loader for the image - after stripping debug symbols), while the actual sbcl.core is ~25MB (all native code and data, loaded into memory).