22:56:04Xachaeth: using preallocated arrays like that is, i believe, an old-ish hack.
22:56:14aethI don't use double floats in many places, and I can't generalize my vector math to doubles because I use multiple return values to avoid consing with single-floats, and that won't work with double floats.
22:56:43aethUnless I extend my multiple return value system to have stack-allocated "registers" of double-floats
22:59:44aethOne other place that will be tricky, probably is text for the UI. I can't preallocate everything there. Maybe I'll have to use some buffer system.
2:36:31antonvWow, http://weitz.de/hunchentoot/ doesn't provide hunchentoot documentation anymore
2:36:50ZhivagoDid he touch you somewhere inappropriate?
2:53:06myrkraverkMy very first asdf system has a name conflict whenever I re-compile it, when I load it with (ql:quickload) however, on subsequent loads, it succeeds.
2:54:23myrkraverkThat is, I have a name conflict in :common-lisp-user and :my-package when I load it with (ql:quickload :my-package) and it needs to compile source file again.
2:57:30myrkraverkI'll try to make a simple example later.
2:59:15Xachmyrkraverk: name conflicts are pretty straightforward to work out up front.
4:09:35aethPCL is more of an introduction. Common Lisp Recipes (same publisher, different author) is more of a reference. I don't think it's online. The ebook was on sale for $10 on Black Friday. So... you'd have to wait almost a year
4:16:50aethThe core language features of Common Lisp haven't been changed in over two decades. The language extensions are a mix between just as old as the language (things that didn't get in the standard, but could have) and fairly new things. They still move fairly slowly. But everything else is just like any other programming language, and it changes over time.
4:17:35aethPCL, noting where it is out of date, is still probably your best option
4:17:47aethThere are other books but they're mostly older