libera/#commonlisp - IRC Chatlog
Search
22:40:34
Oladon
Why does emacs highlight any function that starts with "check-" in red? Is there some convention there I don't know about?
22:45:05
aeth
Those are actual conventions though, while I haven't seen any check- other than the built-in cl:check-type, though
23:27:07
edgar-rft
Oladon: red highlight is probably because of CL:CHECK-TYPE -> http://www.lispworks.com/documentation/lw50/CLHS/Body/m_check_.htm
3:17:23
beach
merazi: http://www.total-knowledge.com/~ilya/mips/ugt.html#:~:text=UGT%20%28abbr.%29%3A%20Universal%20Greeting%20Time.%20UGT%20is%20convention,time%20of%20any%20member%20of%20channel%20is%20irrelevant.
3:20:00
merazi
I'm learning Scheme, a lisp implementation (I know it's not the same as Common Lisp), and I wanted to be part of the lisp community.
3:31:14
beach
merazi: I should tell you, usually #commonlisp is fairly lively, but this is Sunday morning in Europe, and many people here are Europeans with families, so it is a bit slow during the weekend.
3:32:30
merazi
That's completely understandable, I won't be here 24/7 but I'll hang out occasionally.
3:58:11
jcowan
merazi: Not to steal you away or anything, but there is a #scheme channel as well as the #lisp channel, which is about all the Lisps.
3:59:13
merazi
I'm already in the #scheme channel and... *click* Now I am in the #lisp channel as well :)
4:05:55
beach
That dictionary entry says how a conflict should be resolved when an imported symbol conflicts with an existing inherited symbol, and when it conflicts with a symbol that is present.
4:05:59
beach
But what about this scenario: A new symbol conflicts with a symbol that is present, but the present symbol is a shadowing symbol, and there are external symbols in the used packages that would conflict if it weren't for the fact that the present symbol is a shadowing symbol.
4:06:00
beach
So here is my question: Should a conflict be reported that contains also the inherited symbols? If not, what happens if the user uninterns the present symbol? Should the new symbol also be a shadowing symbol right away, or should a new conflict be reported?
4:09:18
beach
I am leaning toward not including inherited symbols in the conflict report and to make it shadowing if the present symbol is a shadowing symbol.
8:57:20
beach
We are accumulating "issues" for WSCL: https://github.com/s-expressionists/wscl/tree/main/wscl-issues/proposed which is good. But we could use some help from people who have easy access to implementations other than SBCL.
8:57:25
beach
Many issues have a line "TODO: check other implementations." where the behavior of other implementations should go.
9:08:20
beach
Some of the issues have been transferred from (I think) Cliki to WSCL. This one was transferred by Bike.
9:09:02
moon-child
yeah, I saw it was dated to 2004, which was why I was surprised I had never heard about it
9:12:59
beach
shka: yes, maybe you prefer to make an "issue" that PROG2 should be deprecated since there is an operator doing the same thing. :)