freenode/#lisp - IRC Chatlog
Search
19:58:33
Inline
pjb: i don't get how paips cmacsyma is not pattern matching when it uses patterns......
20:02:51
kuwze
hey, does anyone know if allegro cl natively supports epoll/kqueue and bypasses the need for something like cl-async?
21:18:10
equwal
So I found a line like this: `(defun add10 (#:m) (+ #:m 10)) at https://github.com/fukamachi/rove and I am curious what the down side of doing it this way is. Why don't we normally do GENSYMS like this?
21:23:21
equwal
It is read into his test framework. I've never seen #:var used outside of a package definition, but I know it is meant to not INTERN the VAR.
21:23:57
pfdietz
Right. So those two #:m will create two different uninterned symbols, each with the symbol-name "M".
21:25:41
pfdietz
Ah, looking at that: the expansion is being printed with *print-circle* = nil. If you set that variable, it will detect the sharing and print appropriately.
21:28:33
pfdietz
The reason names like M are not used is to avoid possible capture. Suppose N was an expression that used a free variable M?
21:29:41
pfdietz
That EXPANDS function he wrote may being played a bit fast and lose? Maybe when it compared uninterned symbols, it just looks at their names?
0:06:49
no-defun-allowed
i assume simple-streams is a layer on top of gray streams providing some simple use cases and setup for streams
0:09:04
scymtym
no-defun-allowed: it is a competing proposal for user-extensible streams: https://franz.com/support/documentation/current/doc/streams.htm#simple-stream-intro-1
0:16:26
no-defun-allowed
but i still would suggest gray streams since that would be implemented in more implementations
0:18:08
ebrasca
Do someone like to read and comment mi ext implementation for mezzano? ( https://github.com/ebrasca/Mezzano/blob/ext-fs/file/ext.lisp )
2:09:00
pierpa
The iterate package available from common-lisp.net has been broken. Anybody knows where to get the usual, working, version?
2:11:33
pierpa
btw, the version at common-lisp.net is not common lisp anymore. I wonder why people do this.
2:23:26
buffergn0me
What is not Common Lisp about https://gitlab.common-lisp.net/iterate/iterate ? Did something change?
2:26:07
pierpa
the first problem is that the third form in the file is (defconst version "1.4" "Current version of Iterate"), which is not CL, and hence does not get compiled by a CL compiler. I have not examined the rest of the source to see what else is broken.
2:31:43
pierpa
loading packages.lisp and iterate.lisp in sequence should work, and it used to work for decades. Now it doesn't.
2:42:34
clintm
Is there a mechanism of any sort that will allow me to iterate over a list and also step backward through that same list? I'm trying to avoid binding a symbol to the previous item, or the like.
2:43:01
pfdietz
Is that different from the ITERATE in QL? That also has a defconst macro in packages.lisp.
2:43:42
clintm
I haven't looked through the docs for iterate past a once-over glance. I'll look again though.
2:44:29
pfdietz
Step backwards? Not that I know of. In general that could be expensive, as ordinary lists do not have back pointers.
2:46:09
clintm
Well, maybe step backwards isn't the best way to describe it, but it looks like iterate's previous keyword is what I'm looking for. Testing it out now.
2:49:25
clintm
I think this is one of those situations where I need to just stop, take my hands off of the keyboard for a minute, and think about what I'm trying to do.
2:51:05
pierpa
this one better: (loop for y = nil then x for x in '(a b c d) do (print (list x y))) ==> (A NIL) (B A) (C B) (D C)