freenode/#lisp - IRC Chatlog
Search
22:58:17
Bike
you have to make _some_ assumption, don't you? that char codes match, or char names match, or something
23:05:43
jasom
well I just tried it on ccl and it confusable-p worked, so it hasn't completely bit-rotted
23:17:38
jasom
(psb-unicode:confusable-p "p" (babel:octets-to-string (make-array 2 :element-type '(unsigned-byte 8) :initial-contents #(#xcf #x81)))) ; => T
4:16:15
mfiano
I'm wondering if such a type declaration would be possible that satisifies the constraint mentioned in the comment: https://gist.github.com/mfiano/bab595782c93421cf8a97671d1e6d30f
4:32:59
Bike
so ub8a is short for a simple-array of (unsigned-byte 8), and the optional parameter controls the dimension specification?
4:33:54
Bike
the fact that you want to treat a bare integer as indicating a single-dimensional array, rather than as a rank, kind of complicates it. without that it would just be `(simple-array (unsigned-byte) ,length)
6:07:04
pyc
What is the difference between these syntaxes: (require "asdf"), (require :asdf) and require ('asdf). The official ASDF documentation recommends the first syntax. Why?
6:25:27
beach
REQUIRE uses string= so it is case sensitive, which would seem like "asdf" and :asdf would not both work, since the second one is converted to "ASDF" by STRING. But if you look at *modules*, it turns out that both "asdf" and "ASDF" are present.
6:31:17
beach
I don't know. What I know is that you need to learn to decipher Common Lisp HyperSpec dictionary entries, which is what I just did, since I don't know these things by heart.
6:33:15
beach
It says it can be a string, a character, or a symbol. If it is a symbol, as in the second and third cases, then the name of the symbol is used. Which is "ASDF" in both those cases.
6:34:26
beach
Now, look at REQUIRE again. It says it uses STRING= to compare the stringified argument to the contents of *MODULES*.
6:35:15
beach
And this is EXACTLY what I did, because I didn't know (or remember) ANY of this stuff.
6:52:50
beach
pyc: If you follow the manipulations I suggested, and that I had to do myself in order to answer your question, then I think you will make it easier to find answers to your questions in the future.
7:27:27
pyc
beach: thanks for the detailed explanation. I am still not familiar with all the terminology used in CLHS but I will keep digging into the docs until it all begins to make sense.
7:56:12
pyc
what does tymoon mean? I see it hosts many lisp channel logs but I can't find its meaning anywhere.