Live data from Hacker News

The KCL Programming Language

github.com

21–27 of 27 posts

Re: The KCL Programming Language

#23
post #19
post #18

Earlier quoted context omitted.

Can you give Kyoto Common Lisp more reference information? I'm interested in it.

Kyoto Common Lisp was developed in the mid 80s in Japan as an independent new implementation. It's a Common Lisp to C compiler. KCL was the first in a family of implementations based on KCL: AKCL, GCL, Delphi CL, ECL, CLASP. The currently usable implementations of those are ECL, CLASP and possibly GCL. For KCL see: https://www.cs.cmu.edu/afs/cs/project/ai-repository/ai/lang/...

[dead]

Re: The KCL Programming Language

#25
I see a problem there with the pythonic range() function. I suggest to create syntax that can express closed, partially closed and open intervals. And make it always requiring two arguments.

As it is now, people have to know the quirks of python to understand what this schema wants to say. The meaning should be clear on first look.

Re: The KCL Programming Language

#27
post #25

I see a problem there with the pythonic range() function. I suggest to create syntax that can express closed, partially closed and open intervals. And make it always requiring two arguments. As it is now, people have to know the quirks of python to understand what this schema wants to say. The meaning should be clear on first look.

Thank you for your suggestion. At first, we expected to make an SRE-friendly language and made enhancements in configuration and policy writing (try to be close to python and shell in use, and use some pythonic built-in functions such as range). However, this does bring additional learning costs to some users who are unfamiliar with python's usage. We will try to eliminate some of python's triks in the future to make the syntax and semantics of KCL clearer.
Post reply on HN