libera/#commonlisp - IRC Chatlog
Search
20:04:22
McParen
I mentioned that earlier because I thought this was a thing, and that thing is not compatible with local nicknames if you refer from A to B and from B to A.
20:06:58
contrapunctus
Recursive dependencies between packages might be a sign of code requiring restructuring...I've managed to avoid them in my CL projects so far, but perhaps that's due to inexperience 😀
20:09:17
Bike
i have also wanted mutual PLNs in the past, which is why i've thought about this stuff. it's not that weird, it just means you have subsystems using each other's APIs
20:15:29
McParen
contrapunctus, that might be correct, but what irks me is that this is not a problem with packages, but just with local nicknames. I dont know about the internals, but it seems weird that people who worked on this api for years let such a "obvious" flaw sli through.
20:16:28
McParen
maybe it was not possible any other way, i dont know. but as I said, today was actually the first time i used PLNs, and i immediately stumbled upon the bug.
20:18:14
McParen
like in: "ok, lets try using local nicknames for a change. *googles sbcl manual* *copy pasta* oh, it doesnt work."
20:25:51
pjb
On the other hand, a function foo remains a function foo, whatever the package she's implemented in.
20:26:29
pjb
alexandria:foo or com.informatimago.common-lisp.cesarum.foos:foo should do the same thing. So using the package and calling (foo …) should be a no-brainer.
20:47:08
jeosol
jcowan Bike: Thanks for your response regarding the Scieneer CL abbreviation. I don't recall seeing any SCL lisp but thought Scieneer CL is abbreviated that way.
22:33:46
brandflake11
Hello, does anyone know of a way, or a package, to get a file's last modified date in common lisp?
22:34:13
brandflake11
Right now, my program is using inferior shell with date -r, but I figured there may be a faster solution
23:46:14
aeth
not actually checking type unless the right implementation/optimization combination is present is so weird
23:46:33
aeth
another thing that's common is not exporting class/type names so you have to check-type on foo::bar
1:40:04
mathrick
Bike: huh! New development. I was looking at the SBCL manual to see if it would help me make sense of of the LDB backtrace, and it mentioned looking at all threads, which I did, and there was a surprising number of them. So I went and disabled loading Verbose, which spawns background threads, and sure enough, the crash is gone
1:40:31
mathrick
I still have no idea why it somehow persists between runs, but at least that's a clue
1:41:38
mathrick
the test code that's crashing isn't even using Verbose for anything, so merely loading it is enough to mess with things