freenode/#lisp - IRC Chatlog
Search
15:44:02
Xach
Wow, that was quick. The author says he has abandoned them due to lack of interest from users and himself.
15:45:15
phoe
Xach: does he have old versions? he could reupload them somewhere and wait for a maintainer.
15:46:14
Xach
I have old versions, but if the author has abandoned them due to lack of interest, I don't think it is good to ask them to do more work with them.
15:46:57
Xach
I will remove them from Quicklisp, and if anyone notices and cares, I will put them on sharplispers.
15:56:42
Xach
I keep a cached checkout of all vcs projects for building Quicklisp dists, so sometimes a project can disappear from its host for a long time before I notice
15:57:03
Xach
I'm going to be more systematic about fetching from the primary source every so often to detect problems with missing or moved projects.
16:57:49
jcowan
aeth: You asked about alists vs. plists: see http://funcall.blogspot.com/2013/07/alist-or-plist.html by Joe Marshall
17:00:17
jcowan
Actually, bignums may not be limited solely by memory: that was written before machine memories grew so big
17:06:39
jcowan
libgmp allows a maximum of 2^2^39, because the number of 64-bit limbs is bounded by a 32-bit signed value.
21:38:35
phoe
when I work with slime-company, I get a string like "-f------" that tells me that a given symbol is bound in the function namespace
22:27:28
conjunctive
Hi, what's the best method for function aliasing? The following gives Quicklisp warnings: (setf (fdefinition '@) #'fset:lookup)
22:31:07
conjunctive
(ql:quickload :zip :verbose t) => ... ;; caught STYLE-WARNING: undefined function: ZIP::@
22:32:37
phoe
try instead doing (eval-when (:compile-toplevel :load-toplevel :execute) (setf (fdefinition '@) #'fset:lookup))
22:35:28
phoe
otherwise, compile-time warnings happen, because the compiler has no idea that things will even out at runtime.
22:35:56
phoe
also, these are not Quicklisp warnings - they are ASDF warnings, or rather, warnings that result from file-compiling your code.
23:13:46
Inline
all of a sudden i have generic functions defined in an earlier package with arguments depending on another package which comes later in the packages.list file not being able to find applicable method therein
2:38:17
Inline
what about the overloading of the same symbol name from different packages whilst they are using other packages via :use directive in their package definition
2:40:18
Inline
i have #:buffer as defclass, as defgeneric (both explicit and implicit via :reader,:writer and :accessor), as defmethod (the same).... the list goes on and on
3:02:19
pjb
Inline: or keep them in a list. Or just scan them from the objects. They're not lost. If they were, they'd be collected!
3:09:22
Inline
am i allowed to refer to class slots as if they were struct slots ? like in struct-name-struct-sloss converted to class-name-class-slot ?
3:11:41
no-defun-allowed
:accessor foo defines a function that can be called with (foo <instance>) and another that can be called with (setf (foo <instance>) <new-value>).
3:11:44
beach
Inline: If you say :accessor <mumble>, then that is the same as saying :reader <mumble> :writer (setf <mumble>)
3:12:56
Inline
i'm not sure what's up here, but i'm getting lots of errors in mcclim and also climacs as a result
3:16:39
pjb
Inline: also, clim doesn't use CL:DEFCLASS, but CLIM:DEFCLASS, so be sure to use the right one.