freenode/#lisp - IRC Chatlog
Search
4:32:23
desvox
also the first comment is "it looks like lisp!" and HAAAAAAAAA anyone who writes lisp anywhere near that needs to have their computers taken away
5:01:24
no-defun-allowed
in lisp at least that kinda thing doesn't look like a cat sat on your keyboard though
5:01:39
no-defun-allowed
it's almost as if...lambdas are half important and aren't munted to hell in cl
5:03:25
no-defun-allowed
then again if you want to do fp in python you may as well mow your lawn with your teeth
6:47:16
fouric
Quicklisp is refusing to load any of my local projects, complaining that it can't locate them.
7:51:18
no-defun-allowed
also, checked you can cd into the symlinked directory? i'm pretty bad at ln and i get symlinks which go nowhere
8:01:59
no-defun-allowed
also, is it a nickname? i'm looking for the mapping that makes COMMON-LISP-USER into CL-USER i suppose
8:10:36
White_Flame
package local nicknames aren't in the standard. Standard nicknames are still global
10:44:21
schweers
Given (defvar *foo* ... ), will (multiple-value-bind (*foo*) ... ) do the same as let?
10:45:26
schweers
The hyperspec says that the variable binding created are exical unless special declarations are specified. I’m not sure if that covers DEFVAR, or if I need extra declarations inside the M-V-B.
10:47:47
schweers
I know, I’m just a little confused by the wording in the hyperspec, as to whether that is sufficient.
10:47:48
jackdaniel
so (defvar *foo* 3) (defun bar (*foo*) (call-something-else)) (bar 14) ; ←← bar will bind variable *foo* to 14
10:49:26
jackdaniel
you can, when defvar / defparameter the compiler "must recognize the name has been proclaimed special"
10:53:21
jackdaniel
estabilishing dynamic context saves you from a nutty api with gazzilion arguments carries just to pass to next function
10:55:20
beach
So many things are nutty. Multiple inheritance, multiple dispatch, first-class packages, first-class symbols, closures. You name it.
10:57:38
jackdaniel
imo it is the way someone uses tools in the box defines whenever code is nutty or not (not the tools themself)
10:58:53
Odin-
jackdaniel: Well, sure. But I've also found it causes a bit of friction when you're dealing with other languages and you're used to having all these (crazy) options that suddenly just aren't there. :)
11:00:16
jackdaniel
sure, dropping to use assembler after you are used to have functions may be tedious, same goes for dropping to C after you are used to closures and when dropping to CL when you are used to monads/hygienic macros/whatever common lisp doesn't seem to have
11:46:02
atgreen
good morning.. I'm looking for something like mapcar that only accumulates non-null results - like a filter. Is there something in the language already for that?
11:49:51
beach
Well, if you are not going to process your element, then (remove nil ...) works as otwieracz suggested.
11:54:22
atgreen
beach: I guess I wasn't clear... I should have said "but only" instead of "that only"?
12:10:10
flip214
Can I ask CFFI whether it found a function (during runtime, because of save/load image!), to provide some fallback?
12:25:21
jackdaniel
you can't also depend on a specific condition across implementation (it simply calls underlying implementation thing)
12:27:42
ogamita
Yes, you can look at cffi::%foreign-funcall to see how it finds the function. It's implementation-dependant.