freenode/lisp - IRC Chatlog
Search
22:46:29
White_Flame
pjb: btw, #. #+ and #- are part of source code, but are not part of serialized "lisp source" as you refer to
22:48:00
pjb
White_Flame: you can look in com.informatimago, there are a few examples of serializing #. #+ #-
22:48:21
White_Flame
sure, you may have created sexpr-level constructs for those, but they aren't part of the lisp core
22:56:45
pjb
White_Flame: and furthermore, #+ #- are very problematic. Try to write a documentation generator on serialized forms full of #+ #-!
23:01:04
White_Flame
serialized means there's some canonical object form that has been converted into a serial form
23:01:56
White_Flame
true it is a "serial" format, but it is not "serialized" from any prior data structure
23:17:45
pjb
White_Flame: there's a data structure in your brain, and again, in com.informatimago and elsewhere, there's code to generate them!
23:18:19
White_Flame
there isn't a data structure in my brain, and even if there were, it's external to the lisp image, so the interface between is still the original source
1:13:47
aeth
asarch: You can open multiple files if you can express them as a wildcard, so C-x C-f ~/your/path/*lisp RET will open all of your lisp files in that directory.
4:28:21
ealfonso
I feel very insecure whenever I just run into 404s and domain errors when trying to find the website of a recommended CL library
4:31:08
ealfonso
https://stackoverflow.com/questions/123234/what-is-the-best-sql-library-for-use-in-common-lisp points to CLSQL (http://clsql.b9.com/ => not found), google search for CLSQL => https://www.cliki.net/clsql => http://clsql.kpe.io/documentation.html => not found
6:25:27
russellw
http://www.lispworks.com/documentation/HyperSpec/Body/f_search.htm - does the test default to eql?
6:30:43
specbot
Satisfying a Two-Argument Test: http://www.lispworks.com/reference/HyperSpec/Body/17_ba.htm
6:30:54
Shinmera
"If neither a :test nor a :test-not argument is supplied, it is as if a :test argument of #'eql was supplied."
7:27:27
specbot
Specifiers for optional parameters: http://www.lispworks.com/reference/HyperSpec/Body/03_dab.htm
7:30:05
Shinmera
no-defun-allowed: ??? optional init-forms are not evaluated if the opitonal argument is given
7:31:54
Shinmera
He's already gone (why do people do that?), but: ((lambda (&optional (a (print "a default"))) a) :a)
8:15:22
pjb
(furthermore, I'm on macOS, I would have to boot a linux box, and I won't have the time today).
8:33:42
White_Flame
I do appreciate that my prior comment was enshrined in the screenshot: https://i.imgur.com/cC3XGdp.png
8:34:15
aeth
paule32: the infix "result" operator that's used in lisp documentation is "=>" so it isn't confused for a valid lisp function like =
8:37:07
adlai
no-defun-allowed: i think paule32 is trying to make an IDE for teaching people how to use nested syntax?
8:40:54
White_Flame
those sorts of parsers are incredibly easy to write, and that's what I thought "+ 1 2 = 3" was implying at first
8:41:17
aeth
"(+ 1 2) => 3" is the correct way to write it, as you would expect to see it in the hyperspec examples. e.g. http://www.lispworks.com/documentation/HyperSpec/Body/f_pl.htm
8:43:19
aeth
Its examples are very clearly for implementors. Do any of the replacements have a better examples section?
8:43:58
paule32
White_Flame: sorry, it comes to picture while i chat with #lisp, sorry, don't imagine it
8:44:30
paule32
pjb: the ide is Qt5 based, Qt5 is a cross development framework for Mac, Linux, and Windows
8:44:31
White_Flame
anyway, my quote that was captured on the snapshot is still important to this whole thing as a whole
8:45:11
adlai
pjb: there was this game i used to play on the toilet, years ago... basically the computer asked the person on the other side of the screen to route a PCB on its behalf. wonderful way to while away a constipated afternoon.
9:24:38
no-defun-allowed
paule32: in common lisp, + at the start of an expression and + in the rest are not equivalent
9:25:36
no-defun-allowed
(+ ...) refers to the function +, whereas (... + ...) refers to the variable + which is defined by your REPL
9:27:21
Shinmera
please stop trying to help him, it is not productive. It's been close to two years of this guy getting advice in this channel and not heeding any of it
10:16:02
russellw
If I understand http://www.lispworks.com/documentation/lw50/CLHS/Body/02_dfa.htm correctly, 'x is equivalent to (quote x) but `x is /not/ equivalent to (backquote x) ?
10:17:55
russellw
sb-int:quasiquote ... guessing that means sbcl-internal, so the representation is purely an implementation detail?
10:19:18
Shinmera
The representation could be handled by a struct or anything, as long as the readably printed variant uses the standard backquote notation
10:33:49
White_Flame
the lack of specification also is a problem if you're walking through code in a macro
10:34:27
White_Flame
there's a fare-quasiquote package which overrides the backquote & comma and ensures it's nice nested sexpr lists for easier traversal