<|3b|>
(if you can't distinguish ∗ and *, try changing font)
<asarch>
I can't even read the letter
<asarch>
Which is which?
<|3b|>
∗ is 'asterisk operator', code-point 8727. * is 'asterisk', codepoint 42
<|3b|>
'∗' and '*', if surrounding with '' helps
<asarch>
WOW!!!
milanj has quit [Ping timeout: 250 seconds]
<asarch>
Yeah!
<asarch>
You're right!
<pjb>
Joys of unicode.
<Xach>
aha! i think ptys on macos can be fixed with some #+/#- fiddling!
<asarch>
Son of the...!!!
<Xach>
cl-expect, here i come!
<|3b|>
probably also some odd quotes in that PDF too, so watch out for those as well
<asarch>
Yeah. I fixed them: ", -, double spaces, etc
<asarch>
Since the beginning, the code was right
<asarch>
#"$#$%$"%$#%"#$!!!
Essadon has quit [Quit: Qutting]
<asarch>
Anyway. Thank you guys
yvy has quit [Read error: Connection reset by peer]
<asarch>
Thank you very much :-)
eddof13 has quit [Quit: eddof13]
<katco>
(i'm sorry for this weird sentence): i'm working on some packaging for guix, and i'm trying to package a package-inferred-system system. with sbcl, guix uses the `compile-bundle-op` to produce fasl's, but this seems to not be working. that is, many fasl files are produced, but not the single `foo--system.fasl` i would expect. is there a way i can get package-inferred-systems to produce this single fasl using the `compile-bundle-op` op?
atgreen has quit [Remote host closed the connection]
atgreen has joined #lisp
<beach>
I will use that as the name of one of my libraries or applications.
<beach>
Just to amuse y'all since it's so quiet here, this is an excerpt from a book on introduction to programming that I am working on: http://metamodular.com/si-units.pdf
<beach>
It is in a chapter about computing with rational numbers.
<beach>
Since there are a very large number of books on introduction to programming, I wanted this one to be different. For one thing, it is using Common Lisp. So it is natural that I show off things like rationals, complex numbers, arbitrary-precision integers, first-class functions, etc.
<beach>
Hmm, nobody is amused. Oh well. I guess it won't be a bestseller then.
<Xach>
Needs time for word-of-mouth
<makomo>
beach: the name "CLOStrophobia" or "claustrophobia" or something else? :-)
<beach>
makomo: The former.
<beach>
I guess both really.
<beach>
Xach: Needs to be finished first of all.
<makomo>
now that's pretty neat. do you have an idea of what the library/application will do?
<beach>
No. :)
<makomo>
heh :-)
<jackdaniel>
it may bring some confusion (because this article is known for this name)
<jackdaniel>
by this name°
<beach>
Hmm, yes, you are right.
<makomo>
beach: i think you have an extra space before the closing paren in the output of your example in si-units.pdf
<beach>
I do, yes.
<beach>
I might try to get rid of it.
<beach>
Normally, I would delegate that kind of work to my coauthor, but none has been named for this book yet.
<makomo>
ah
benkard has joined #lisp
atgreen has quit [Ping timeout: 258 seconds]
KingRiver has joined #lisp
ft has quit [Ping timeout: 250 seconds]
meepdeew has joined #lisp
wxie has quit [Quit: Bye.]
Younder has joined #lisp
undiscovered has joined #lisp
smokeink has quit [Quit: Leaving]
orivej has quit [Ping timeout: 245 seconds]
wxie has joined #lisp
anewuser has joined #lisp
atgreen has joined #lisp
meepdeew has quit [Remote host closed the connection]
wxie has quit [Quit: Bye.]
<Xach>
Hmm
ntbre has joined #lisp
<Xach>
When looking for patterns in streams from arbitrary sources (not necessarily well-encoded, or possibly with control codes, etc) I've often thought it would be better to convert the pattern to binary, rather than convert the whole stream all the time according to some encoding. And then only convert the potentially-small data of interest to character data. But I've only tried it on a small scale so I'm not sure
<Xach>
how well it would work for bigger things.
<Xach>
It's on my mind today because of a renewed interest in something Expect-like in sbcl, where the program output often has a lot of junk in it.
xrash has joined #lisp
<Younder>
How do you intend to determine what pieces are character data?
<Xach>
Younder: in the past i've used protocol context. for example, http headers have line terminators and colons that mean special things.
<Xach>
so checking for the ascii codes 10 and 13 and 58.
MichaelRaskin has quit [Quit: gchristensen last call: if nobody is in the process of writing a good post about medium-term RFC SC selection rules, I will write a quick-hack «please state your opinions» one]
angavrilov has quit [Remote host closed the connection]
akoana has joined #lisp
akoana has left #lisp [#lisp]
<dim>
fiddlerwoaroof: wow, I'm interested! for pgloader
<dim>
well I think I misunderstood what you said here, too bad
JetJej has quit [Quit: [Quit]]
Khisanth has joined #lisp
metallicus has joined #lisp
notzmv has joined #lisp
xrash has quit [Ping timeout: 244 seconds]
<fiddlerwoaroof>
dim: what did you think I said?
<fiddlerwoaroof>
The reason I did all this work is that CFFI generates runtime dependencies on shared objects that make it hard to transfer a dumped lisp image to someone else's system
mulk has quit [Ping timeout: 240 seconds]
<fiddlerwoaroof>
(osicat is the worst offender here, ime, because it generates a so as part of its build in the ASDF cache directories)
mulk has joined #lisp
<fiddlerwoaroof>
I've been hoping to see if I can get pgloader to use this build process
<fiddlerwoaroof>
(you asked me about it a couple months ago, but things have been kinda crazy around here)
xrash has joined #lisp
atgreen has joined #lisp
charh has quit [Remote host closed the connection]