tynet-lichat/shirakumo - IRC Chatlog
Search
Friday, 14th of January 2022, 21:33:35 UTC
22:11:44
shinmera
scymtym: i have an experimental change here https://github.com/Shirakumo/lichat-protocol/tree/parsed-protocol
22:13:19
shinmera
scymtym: Ensures that the protocol classes are accurate to the spec files, but will break stuff like defaulting initargs. Also unsure if it handles required slots correctly yet, I'd like to tackle that in the printer as well (treating unbound as unset rather than NIL)
22:13:32
shinmera
scymtym: Let me know what you think
22:14:11
Colleen
i will have a look later
22:14:11
scymtym
i will have a look later
22:14:19
shinmera
Sure, no rush. I'm about to sleep anyway :)
22:16:03
shinmera
SAL9000-: Might also want to look at the changes, since we should follow the same lead in the python lib.
23:06:53
SAL9000-
Hm, I'm guessing the existing wire.py reader should be able to eat the sexpr files?
6:43:46
shinmera
Yes, almost. I had to make two particular hacks in the lichat one
6:43:57
shinmera
1) it needs a mode where it'll intern symbols instead of replacing them with unknowns
6:44:20
shinmera
2) it needs a temporary hack to alias the shirakumo package with the lichat package, since currently all clients and servers do that
6:50:19
shinmera
err, in the lisp one
8:06:01
shinmera
Oh and I forgot to mention but in my sleep addled brain I could not figure out how to implement define-object-extension
8:06:09
shinmera
(I still can't without complicated mop fuckery)
8:35:38
shinmera
Also just noticed the lichat server is eating 200% CPU? what in the fuck
8:44:09
shinmera
Anyway, guess I have to restart that server
8:46:30
shinmera
The patches for backfill etc. are in now at least
8:46:41
shinmera
and I have a thing I can use to debug performance problems like this in the future
8:47:02
shinmera
Or, not performance, but likely some bad recursion?
Saturday, 15th of January 2022, 9:33:35 UTC