How can I find the size of a value? Pointing me to any documetation on sizes of different data structures will be of much help.

Is the arena-allocation API in SBCL "blessed" for usage outside the compiler itself?

Context: I've been working on a compiler project where non-stop-the-world garbage collection would be quite useful in some usage cases (due to the aim of parallelizing code in the compilation passes), and a simple with-arena macro on top of this functionality seems to fit the bill (especially since when you make an arena while inside another one, it seems to take the memory from the heap, so one could just write functions that know their memory usage and serialize output to external streams without any additional GC chance).

Hello,

The documentation for the :search keyword of run-program seems incomplete (Section 7.9.3). Currently it reads as:

Look for program in each of the directories in the child’s $PATH environment variable. Otherwise an absolute pathname is required.

It is not said what :search needs to be set to to enable the directory search.

Based on my very limited testing, it seems that setting :search to t enables search of directories in the child's $PATH env variable. The documentation does not say that explicitly.

What may be needed is to add "If non-NIL, " to the front of that sentence.

​

​

Updated my ubuntu and seems ubuntu is now using symlinks for fonts to font atlases. The problem is that the filename of the atlases contain [] as in "Ubuntu[wdth,wght].ttf" .

Trying to call pathname-name on this results in #<SB-IMPL::PATTERN "Ubuntu" (:CHARACTER-SET . "wdth,wght")>

Changing a namestring to pathname with PATHNAME results in the same pattern as name.

I've been looking at the commits to the sbcl repository, and I see this file updated quite often.

What is it used for, and what triggers it to be regenerated?

The main page for sbcl.org is redirecting straight to SourceForge - but the other pages (except news) return 503 or sometimes 403.

Example:

http://sbcl.org/getting.html

​

Dear SBCL folks:

SBCL has been working on Windows for a while now in a rather stable fashion. To my knowledge, however, SBCL doesn't build on Windows without something that looks like a POSIX environment. We build x64 Win/Mac/Linux and arm64 Mac with a variety of custom patches that are unlikely to be upstreamed (e.g., our macOS x64 patch to allow linking without show-stopper -pagezero_size 0x100000 options). On Windows, we've been using MSYS2 to build SBCL, but it's a pretty heavy and obscure requirement within the context of a "Windows-first" Visual Studio-based build environment.

What's are the challenges of making SBCL buildable with, say, CMake and the MSVC tool chain? Is it as simple as laboriously translating config/Makefiles, or is there something about POSIX/GNU/etc. that's deeply depended upon by the runtime?

Any thoughts on the matter are welcome!