LiutCL | 主动挖坑并打算努力填坑的一个简陋的Lisp解释器

by Liutos C Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | LiutCL Summary

LiutCL is a C library. LiutCL has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

主动挖坑并打算努力填坑的一个简陋的Lisp解释器

Support

Quality

Security

License

Reuse

Support

LiutCL has a low active ecosystem.

It has 32 star(s) with 4 fork(s). There are 6 watchers for this library.

It had no major release in the last 6 months.

There are 5 open issues and 3 have been closed. On average issues are closed in 1142 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of LiutCL is current.

Quality

LiutCL has no bugs reported.

Security

LiutCL has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

LiutCL does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

LiutCL releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of LiutCL

Get all kandi verified functions for this library.

LiutCL Key Features

No Key Features are available at this moment for LiutCL.

LiutCL Examples and Code Snippets

No Code Snippets are available at this moment for LiutCL.

Community Discussions

No Community Discussions are available at this moment for LiutCL.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install LiutCL

You can download it from GitHub.

Support

在lambda中无法使用完全的ordinary lambda list 这是因为调用由lambda构造出来的函数等价于在扩展过的词法环境中去依次求值函数体的代码，而这个扩展的过程是由函数extend_env_by_cons完成的。但是这个函数的功能很简单，无法识别出一个对象究竟是specifier还是parameter，所以它会把specifier当作参数名进行处理，这样会导致扩展出来的词法环境多了绑定，而且顺序也不对。既然单纯地把参数列表和值联系起来是错误的，那么就应该结合一些其它信息来决定将哪一个参数名和哪一个值联系起来。这样的信息显然应该是根据lambda-list得出来的，大概可以猜测到包含下面这些信息：必要参数的数量；可选参数的数量；可选参数是否有初始值；可选参数是否有对应的-p参数；是否有&rest限定符；关键字参数的数量；关键字参数是否指定了关键字名字（当关键字参数被置于两重cons中时，第二重cons的car即为关键字名字）；关键字参数是否指定了初始值；关键字参数是否有对应的-p参数；是否有&allow-other-keys限定符；是否有aux参数； aux参数是否有初始值。

Find more information at: