tynet-lichat/shirakumo - IRC Chatlog
Search
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
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
13:08:59
shinmera
I kinda want to separate the lichat protocol definition from the CL lichat package, but not sure yet if I should.
13:10:29
SAL9000-
having the reference implementation in the same repo as the machine-readable spec *kinda* makes sense?
13:11:08
shinmera
It long ceased being that though and has some peculiarities that don't translate well
13:11:47
SAL9000-
in that case, moving the CL implementation out would leave a repo with the human-readable spec + the machine-readable spec, which is also a good combination
13:12:24
SAL9000-
then the spec can be a submodule (or subtree) in each of the implementations, representing the version of the spec that the implementation supports
13:13:13
SAL9000-
afaik this *is* one of the use-cases where submodules actually make sense for once :P
13:18:06
SAL9000-
well, you currently have lichat = the website, lichat-protocol = the spec + CL impl
13:21:07
shinmera
I wouldn't mind changing lichat/master to lichat/web or whatever, and then making master be the spec
13:21:55
SAL9000-
hm... that makes subtree more of a requirement to avoid pulling in web along with spec I guess
14:00:41
shinmera
Now that we have a separate repo for the spec, I can also finally tear the shirakumo extensions out of the core document.
14:03:23
Colleen
Shinmera: fyi parsed-protocol pylichat is broken; trying to figure out how to fix it
14:03:23
SAL9000
Shinmera: fyi parsed-protocol pylichat is broken; trying to figure out how to fix it