5:15:41jmercouristhe voice in this paper sounds so much like you on IRC
5:24:14jmercouristhe only thing I am worried about is that the diff will show changes when I type in M-q to limit the width of the paragraphs showing false changes
6:14:15mfianobeach: I recall you once had a great argument against using the :TYPE slot option for DEFCLASS slots. I can't seem to find that in my logs. Care to repeat your view on that matter?
6:16:05beachmfiano: I think it was just the ordinary argument against manifest typing, i.e., that it forces the programmer to provide information early in the life of some software, and this information is often incorrect later on, so it creates a lot of maintenance later on.
6:17:00mfianoThat is fair. I think that much more applies to documentation, though. I have seen docstrings that don't agree with the following code much more often.
6:18:51beachAnd comments too, where the programmer thinks that more comments always provide more information. But then they have to be kept in sync with the code.
6:21:39mfianoI agree a little too much on the matter, that it sometimes hurts me. Until my software is release-ready, which is takes a long time if ever, I don't provide documentation anymore. I do however maintain offline Orgmode outlines for larger projects to help me organize my thoughts and prepare for the future when I will write real documentation -- and by real, I mean offline documentation with examples, diagrams,
11:40:47hajovontahow can I declare a function definition ignorable? I have some created with flet, that I don't use in a particular macroexpansion, and SBCL style-warns about deleting unused functions
15:28:11mitc0185I am starting a side project using GNU Common Lisp -- part of the fun is using something that's a bit dated. Any words of caution before I go too far down this road? Should I use a different distribution?