contrapunctus has left #lisp ["Disconnected: closed"]
contrapunctus has joined #lisp
contrapunctus has left #lisp ["Disconnected: closed"]
contrapunctus has joined #lisp
luckless_ has joined #lisp
amerlyq has quit [Quit: amerlyq]
miasuji has joined #lisp
Inline has joined #lisp
gaqwas has quit [Ping timeout: 256 seconds]
phoe6 has joined #lisp
contrapunctus has left #lisp ["Disconnected: closed"]
quazimod1 has quit [Ping timeout: 240 seconds]
contrapunctus has joined #lisp
todun has quit [Quit: todun]
abhixec has joined #lisp
abhixec has quit [Client Quit]
contrapunctus has left #lisp ["Disconnected: Replaced by new connection"]
contrapunctus has joined #lisp
miasuji has quit [Ping timeout: 260 seconds]
kaftejiman_ has quit [Ping timeout: 260 seconds]
<antonv>
phoe: maybe modern mode is not a minefield, other way around, classic mode is a minefield, we just have a shifted perspective
<antonv>
modern mode is more straightforward - symols are named exactly as written
KREYREEN has joined #lisp
KREYREEEN has quit [Ping timeout: 240 seconds]
kaftejiman_ has joined #lisp
wxie has joined #lisp
kaftejiman_ has quit [Remote host closed the connection]
kaftejiman_ has joined #lisp
contrapunctus has left #lisp ["Disconnected: closed"]
contrapunctus has joined #lisp
contrapunctus has left #lisp ["Disconnected: Replaced by new connection"]
contrapunctus has joined #lisp
contrapunctus has left #lisp ["Disconnected: closed"]
kaftejiman_ has quit [Remote host closed the connection]
karlosz has quit [Remote host closed the connection]
kaftejiman_ has joined #lisp
Lycurgus has joined #lisp
<thmprover>
Say, are there any good references on *implementing* Common Lisp?
contrapunctus has joined #lisp
<Xach>
thmprover: common lisp specifically, no. but Lisp in Small Pieces and Anatomy of Lisp both get into some pretty detailed nuts and bolts of lisp compilation.
<Xach>
there is a detailed document on the implementation of cmucl i believe
<Lycurgus>
use the source luke
<thmprover>
I do like LiSP, I'll lookup "Anatomy of Lisp"
<Xach>
i think frodef used Anatomy of Lisp to implement movitz's compiler
<Xach>
you might ask froggey what he used for mezzano
tempest_nox has quit [Ping timeout: 240 seconds]
<thmprover>
The 122 page document "Design of CMU CL" by Robert MacLachlan, is that the one you're referring to, Xach?
contrapunctus has left #lisp ["Disconnected: Replaced by new connection"]
contrapunctus has joined #lisp
luckless_ has quit [Remote host closed the connection]
luckless_ has joined #lisp
contrapunctus has left #lisp ["Disconnected: closed"]
contrapunctus has joined #lisp
<beach>
thmprover: If you are interested in how Common Lisp is implemented, we have regular discussions in #sicl, and you are welcome to participate.
<beach>
... participate and ask questions.
<beach>
thmprover: Mostly, Common Lisp is a fairly ordinary language from the point of view of compilation. Other aspects are not so ordinary, like how CLOS is implemented.
Bike has quit [Quit: leaving]
<p_l>
outside of some "rarer" features like multiple returns, which complicate calling conventions (unless one runs on MMIX), everything else is optimization question
<beach>
Right. There are some quirks like that. Otherwise, the hard part is making it all fast.
wxie has quit [Ping timeout: 264 seconds]
<thmprover>
beach: cool, that sounds like what I'm after.
rippa has joined #lisp
thmprover has quit [Quit: Up, up, and away]
andreyorst has quit [Ping timeout: 260 seconds]
charles` has quit [Ping timeout: 260 seconds]
jibanes has quit [Ping timeout: 268 seconds]
jibanes has joined #lisp
rippa has quit [Quit: {#`%${%&`+'${`%&NO CARRIER]
jibanes has quit [Ping timeout: 240 seconds]
jibanes has joined #lisp
bisickcor has quit [Ping timeout: 256 seconds]
bisickcor has joined #lisp
froggey has quit [Ping timeout: 246 seconds]
ldbeth has joined #lisp
<ldbeth>
good afternnon
froggey has joined #lisp
<beach>
Hello ldbeth.
wxie has joined #lisp
elflng has quit [Read error: No route to host]
andreyorst has joined #lisp
rumbler3_ has quit [Remote host closed the connection]
rumbler31 has joined #lisp
narimiran has joined #lisp
elflng has joined #lisp
narimiran has quit [Ping timeout: 264 seconds]
narimiran has joined #lisp
luckless_ has quit [Ping timeout: 240 seconds]
luckless_ has joined #lisp
<lotuseater>
beach: do i need my acc to be registered for joining #sicl?
<beach>
lotuseater: I have no idea.
<ck_>
lotuseater: yes, you do
<beach>
ck_: Thanks!
* beach
needs a channel administrator.
<lotuseater>
ok, my client didn't respond so explicit
<ck_>
beach: does that channel need much administering?
<beach>
ck_: No, not usually. But last night there was a long discussion that I didn't appreciate at all. It would have been enough to be firm though, because all the participants are known and frequent.
<ck_>
I see
<lotuseater>
ok I'll think about registering and will ask then if it's ok to join
<beach>
It is always OK to join if you can.
imode has joined #lisp
luni has joined #lisp
andreyorst` has joined #lisp
andreyorst` has quit [Remote host closed the connection]
andreyorst has quit [Ping timeout: 264 seconds]
andreyorst` has joined #lisp
uplime has quit [Disconnected by services]
also_uplime has joined #lisp
also_uplime has quit [Disconnected by services]
also_uplime has joined #lisp
wooden has joined #lisp
wooden has quit [Changing host]
wooden has joined #lisp
amerigo has joined #lisp
ik` has joined #lisp
zulu-inuoe has quit [Read error: Connection reset by peer]
ik` has quit [Quit: ERC (IRC client for Emacs 26.3)]
karlosz has quit [Quit: karlosz]
frost-lab has joined #lisp
aindilis has quit [Ping timeout: 246 seconds]
asarch has joined #lisp
amerigo has quit [Read error: Connection reset by peer]
gendl has quit [Ping timeout: 246 seconds]
amerigo has joined #lisp
gendl has joined #lisp
shka_ has joined #lisp
ldbeth has left #lisp ["ERC (IRC client for Emacs 27.1)"]
<Alfr>
phoe, on (setf aref): The setf function may simply be undefined, clhs 5.1.1.2 last paragraph. (Though I may have missed an explicit exception for aref.)
<phoe>
there is an explicit exception for aref AFAIR
<phoe>
there's apply exceptions for aref, bit, and sbit AFAIR
andreyorst` has quit [Quit: andreyorst`]
<pfdietz>
For each standardized accessor function F, unless it is explicitly documented otherwise, it is implementation-dependent whether the ability to use an F form as a setf place is implemented by a setf expander or a setf function. Also, it follows from this that it is implementation-dependent whether the name (setf F) is fbound.
<pfdietz>
Which you are referring to
<Alfr>
phoe, you mean 5.1.2.5? That equivalence (mod evaluation order) is only required for user-defined functions.
<Alfr>
jackdaniel, will try messing w/ warning some time, thanks.
matryoshka has joined #lisp
<jackdaniel>
warnings will only give you your own screwups, they are not about strictness wrt conformance
<jackdaniel>
also you probably want to thank jmercouris, I did not suggest that
__jrjsmrtn__ has quit [Ping timeout: 256 seconds]
<jmercouris>
I think some warnings might show non conformance
<pfdietz>
Also, all the code that does something like (apply #'append <list>) on lists of length > 50.
<jmercouris>
never tried it explicitly though
<phoe>
yes
<pfdietz>
Code that assumes that for fixnums EQ and EQL mean the same thing.
<phoe>
actually
<phoe>
pfdietz: ABCL has call-arguments-limit at 50
<jackdaniel>
some people have an impression, that bignums can be arbitrarily big, however it is only said, that there is no limit on the magnitute of an integer -- I *think* that it would be conforming to signal a storage condition on (1+ most-positive-fixnum) :-)
<phoe>
jackdaniel: :D
<jackdaniel>
of course it would be outraging to do so
<Alfr>
jackdaniel, yeah good point and damn completions.
<phoe>
you people are awful
<phoe>
I love it
<Alfr>
And thanks jmercouris. ^ :)
<jmercouris>
no problem Alfr
<pfdietz>
The random tester would sometime generate code that failed in the sbcl type propagator because of a loop that successively squared a variable. The bignums grew too big to store.
contrapunctus has left #lisp ["Disconnected: closed"]
contrapunctus has joined #lisp
miasuji has quit [Ping timeout: 260 seconds]
Jeanne-Kamikaze has joined #lisp
gko_ has quit [Ping timeout: 265 seconds]
luni has joined #lisp
attila_lendvai has joined #lisp
miasuji has joined #lisp
karlosz has joined #lisp
andreyorst has joined #lisp
jjong has quit [Ping timeout: 246 seconds]
EvW has quit [Ping timeout: 268 seconds]
cosimone has quit [Quit: cosimone]
Inline has quit [Ping timeout: 264 seconds]
luni has quit [Quit: Connection closed]
jibanes has quit [Ping timeout: 264 seconds]
EvW has joined #lisp
jibanes has joined #lisp
<loke[m]>
How can I tell what GIT repository a given QL system uses? In particular, I'm trying to fix a bug in cl-cffi-gtk, but what I believed was the official release doesn't seem to be since the content doesn't quite match what's on QL. Clearly QL uses a different fork.
<ck_>
I thought that was in quicklisp-projects, the repository
<phoe>
wait a second, there's a breakage of mine in there...
* phoe
fixes
EvW has quit [Ping timeout: 268 seconds]
<mfiano>
Xach: Was the breakage due to SBCL being more conformant, or what?
EvW has joined #lisp
<mfiano>
I see the library hasn't been updated in 5 years anyway
<phoe>
yes, SBCL did not detect this as a compile-time error, and now it does'
v88m has quit [Ping timeout: 246 seconds]
mankaev has quit [Read error: Connection reset by peer]
mankaev_ has joined #lisp
* phoe
fixed PCS
karlosz has joined #lisp
<phoe>
oh, sheeple is also affected by it
EvW has quit [Read error: Connection reset by peer]
EvW has joined #lisp
* mfiano
would be happy if cl-sdl2-ttf was just removed from QL
<mfiano>
It improperly uses finalizers more than 2 years after I changed cl-sdl2 to not use finalizers. The library just plain does not work without memory faults (at runtime), and the author has been unresponsive.
<mfiano>
Therefor, I think it being in Quicklisp is not helping anyone, since it just plain doesn't work at all.
<Xach>
Ok
EvW1 has joined #lisp
EvW has quit [Ping timeout: 268 seconds]
EvW1 is now known as EvW
KREYREEN has quit [Remote host closed the connection]
Aurora_v_kosmose has quit [Remote host closed the connection]
madage has quit [Write error: Broken pipe]
cantstanya has quit [Write error: Broken pipe]
gxt has quit [Write error: Broken pipe]
gxt has joined #lisp
KREYREEN has joined #lisp
Aurora_v_kosmose has joined #lisp
madage has joined #lisp
<mfiano>
Or maybe it should be moved to sharplispers, if someone is willing to fix it.
judson_ has joined #lisp
<attila_lendvai>
there's also hu.dwim.sdl which is autogenerated and IIRC complete
cantstanya has joined #lisp
<mfiano>
There's nothing wrong with cl-sdl2
<mfiano>
It's the ttf extension binding
<mfiano>
Oh I see that it includes the extensions too
orivej has quit [Ping timeout: 260 seconds]
Lord_of_Life_ has joined #lisp
luni has joined #lisp
Lord_of_Life has quit [Ping timeout: 264 seconds]
Lord_of_Life_ is now known as Lord_of_Life
lucasb has joined #lisp
luckless_ has joined #lisp
galex-713 has quit [Ping timeout: 260 seconds]
Lord_of_Life has quit [Ping timeout: 246 seconds]
bisickcor has joined #lisp
Lord_of_Life has joined #lisp
iekfkk has quit [Ping timeout: 246 seconds]
EvW has quit [Remote host closed the connection]
EvW has joined #lisp
galex-713 has joined #lisp
rumbler31_ has joined #lisp
Jesin has quit [Quit: Leaving]
rumbler31 has quit [Ping timeout: 265 seconds]
Jesin has joined #lisp
karlosz has quit [Quit: karlosz]
birdwing has quit [Ping timeout: 240 seconds]
andreyorst has quit [Ping timeout: 260 seconds]
karlosz has joined #lisp
rogersm has quit [Quit: Leaving...]
puchacz has joined #lisp
notzmv has quit [Ping timeout: 260 seconds]
<puchacz>
hi, when I have an error inside unwind-protect, and I choose "abort thread" or similar restart, the cleanup clause from unwind protect is not executed. any workaround for it please?
<puchacz>
I use sly but slime is probably similar
cosimone has joined #lisp
jprajzne has quit [Quit: Leaving.]
<pfdietz>
"Fixed bug in sheeple where it wasn't waking up."
aindilis has joined #lisp
jibanes has quit [Ping timeout: 264 seconds]
jibanes has joined #lisp
<puchacz>
okay, " 1: [*ABORT] Return to SLY's top level." evaluates the cleanup
<eta>
puchacz: yeah aborting the thread, uh, aborts the thread
<eta>
it's like kill -9 for threads
<eta>
you don't get to clean up
<puchacz>
eta - yes, fortunately this "return" works fine. maybe it calls return-from
<puchacz>
in SLY, abort thread restart kills the current REPL as well, so not very convenient
<eta>
puchacz: SLY probably wraps repl evaluations in the equivalent of a WITH-SIMPLE-RESTART
<puchacz>
but I guess the logic is consistent
Aurora_v_kosmose has quit [Remote host closed the connection]
<eta>
you should avoid aborting threads if you don't need to :p
<puchacz>
easy to hit the button by mistake :)
Aurora_v_kosmose has joined #lisp
<puchacz>
anyway, I am good with 1: [*ABORT] Return to SLY's top level.
<puchacz>
tks :)
<eta>
no problem!
<eta>
puchacz: protip, pushing "a" should choose that one
<eta>
at least I think it does that for my SLIME setup
<puchacz>
*a means that?
<mfiano>
Hitting "a" selects the to-most abort restart, yes
<mfiano>
top-most*
<mfiano>
Likewise "c" for top-most continue
<puchacz>
it is the second abort, first is to re-evaluate, number 0