freenode/#lisp - IRC Chatlog
Search
20:13:06
White_Flame
rodriga: usually, the macro-based customization of CL is focused around creating the proper abstractions for your codebase, which just gives a few enhancements and interacts well with CL in a very readable way, not it's own completely separate languages
20:31:55
Josh_2
Yes, basically the old functionality just locally bound *standard-output* so that I could grab the output and send it over a socket, but then I swapped my logging system to log4cl and this obviously broke
20:38:55
jackdaniel
you will need to check that in the source code, but if I remember correctly the appender protocol consists of a single method
20:40:27
jackdaniel
that said, from what you have said you expect it to intercept messages to the standard output - that's not how log4cl works
21:42:08
Xach
phoe: I don't think it was tagged as a release on github. at least as of early this morning.
22:05:47
jcowan
I confess to not looking at examples when I read specs (they are often misleading or outright wrong in my experience)
22:06:26
Bike
well that's all i got. what it's actually been developed for so far is using it in compilers, tho.
22:06:49
jcowan
There are a few problematic specs where the examples are normative either de facto or de jure
23:23:10
jasom
Is there a library that makes a non-seekable stream (somewhat) seekable by adding buffering on top? I'm thinking something that guarantees always allowing seeking back N elements (up to the beginning, where N >> 1 and is possibly configurable)
23:28:16
mfiano
A Gray stream wrapper for that would be only a couple lines of code not even worth a library
3:30:55
jasom
mfiano: it's not the number of lines of code, it's how long it takes to write the lines of code. I've written something similar before and I had some subtle bugs with my first implementation.