freenode/lisp - IRC Chatlog
Search
12:58:42
jackdaniel
fe[nl]ix: re barriers documentation: https://gitlab.com/embeddable-common-lisp/ecl/-/merge_requests/225
13:00:00
jackdaniel
for those who are interested in ecl history, the graph of inheritance has changed - apparently ECL is a descendant of DELPHI Common Lisp (the history chapter is updated)
13:03:02
gendl
jackdaniel: history chapter? Is there a book going on that i've missed? (I don't keep up in this channel enough..)
13:04:01
jackdaniel
gendl: ECL's manual has a chapter "History", in this pull request I've incorporated some information kindly provided by professor Attardi
14:57:56
sjl_
Interesting. That doesn't break anything else? Any why do you need it after every sublist? Won't a single &optional at the beginning do the same thing?
14:59:13
sjl_
I was thinking it was going to do (&optional x &optional y &optional z). Haven't had coffee yet.
15:57:56
Bike
the actual issue this person is complaininga bout is that ccl doesn't detect the type mismatch, but of course there's no requirement to do so
19:11:01
aeth
phoe: To be fair, anything that prints to *standard-output* can print to `(with-output-to-string (*standard-output*`... and be grepped with cl-ppcre, so while not ideal, it technically provides a "Lisp value"
19:14:57
aeth
I think I'd call it a "fragile value" or something if it's in a string. Yeah, you can get it, but it is even less protected from breaking than normal implementation internals.
19:15:13
aeth
(a string or a stream, which are essentially equivalent if you want the data since you can turn one into the other)
19:16:53
aeth
(to be really technical, equivalent in this particular use case... obviously you can e.g. have an interactive stream or something like that)
21:36:14
ralt
it is probably a dumb question, but how do you set bitflags? I have 16 bits where I want to set some bit flags, and having to have each bit flag being e.g. #*0000000000000001 sounds a bit... wasteful
21:41:34
ralt
like, one of my flags is #*0000000000000001, so I can run (bit-ior ... my-flag), but is there a better way to write my-flag then (defvar my-flag #*0000.....1)?
21:45:28
ralt
ok, a way that is just as verbose but at least not error-prone (because I get an error if the number of elements don't match) is `(make-array 16 :element-type 'bit :initial-contents '(0 0 0 0 ..... 1))`
21:48:30
ralt
I'd have to convert the unsigned-byte array into a bit array in order to run BIT-IOR on it