fare / lisp-interface-library Goto Github PK

View Code? Open in Web Editor NEW

144.0 25.0 17.0 559 KB

LIL: abstract interfaces and supporting concrete data-structures in Common Lisp

Common Lisp 97.36% Racket 1.45% NewLisp 1.18%

lisp-interface-library's Introduction

lisp-interface-library

LIL: abstract interfaces and concrete data structures in Common Lisp

Home Page: http://github.com/fare/lisp-interface-library/
We wrote an article explaining about our library for ILC'2012: http://github.com/fare/lil-ilc2012/
A PDF of a slightly corrected version of the article is here: http://common-lisp.net/~frideau/lil-ilc2012/lil-ilc2012.pdf
An HTML of that version of the article is here: http://common-lisp.net/~frideau/lil-ilc2012/lil-ilc2012.html
A short introduction on our "Interface-Passing Style" of programming, is also at: http://fare.livejournal.com/155094.html
Manual: I have never worked on a manual, nor on a tutorial. For a quick introduction to how things work, look at the tests in test/ for a few examples. Then docstrings and source code can get you somewhat further. A manual or a tutorial would be a great contribution to this library.

Features

LIL nicely combines ad-hoc polymorphism (CLOS-powered object oriented programming) and parametric polymorphism (as in ML functors, C++ templates, etc.). To our knowledge, only scalaz matches the expressiveness of LIL.
LIL sports both pure (persistent, immutable) and stateful (ephemeral, mutable) variants of data structures in Interface-Passing Style. This variants are in the respective packages PURE and STATEFUL; a common core is shared in package INTERFACE, covering read-only operations; automatic transforms allow bridging from stateful to pure and back.
LIL supports data structures in traditional Object-Oriented Style, in both stateful (the usual Object-Oriented kind) and pure variants, in the respective packages POSH and CLASSY. There too, automatic transforms to go from Interface-Passing Style to traditional Object-Oriented Style and back.

Building it

LIL needs to be built using ASDF 3.1 or later:

Indeed, LIL notably relies on ASDF 3.1's package-inferred-system. whereby instead of dependencies being listed in a central .asd file, each source file has a defpackage form from which the dependencies are deduced. While we think it's a great way to write Lisp code, you don't have to use it in your own code to use LIL.

LIL also depends on fare-utils, fare-memoization, closer-mop, alexandria.

Using it

See test/pure-map.lisp and test/stateful-map.lisp for examples of how to use LIL. Unhappily, no one is working on documentation at this time.

lisp-interface-library's People

Contributors

Stargazers

Watchers

Forkers

danlentz drewc priyadarshan tmccombs shiva16 makarovalexey dalekbaldwin xuntiange vliviu cl-kuthirgal icodein ashok-khanna pallas42 bohonghuang daninus14

lisp-interface-library's Issues

Does not build today on SBCL 1.4.5

http://report.quicklisp.org/2018-03-26/failure-report/lisp-interface-library.html#lil has the log.

I get an error related to fare-memoization, which I get from https://gitlab.common-lisp.net/frideau/fare-memoization.git

add user manual documentation

This looks like a really interesting library, and I like the interface passing style. However, I can't find any user documentation. The article referenced in the README does a good job of explaining interface passing style, but not how to actually use this library. I would like some documentation and examples of how to actually use lisp-interface-library, and what data structures are available.

License line in all ASDF files

Hi Fare,

would you mind putting :license "MIT" in all of the ASDF files so that a full dependency tree shows complete license coverage?

Thank you so much.

Decide which is the official repository

@guicho271828 has moved issues from the TODO file to his repository:
https://github.com/guicho271828/lisp-interface-library/issues

Make sure all the issues are either tracked there (if it becomes the "official" repository), or here (by migrating them from there), or wherever the official repository ends up being.

Update/remove dead links to the LiL paper in README.

The following links mentioned in the README seem to be dead (404 errors)

https://common-lisp.net/~frideau/lil-ilc2012/lil-ilc2012.pdf
https://common-lisp.net/~frideau/lil-ilc2012/lil-ilc2012.html

TODO in github issues rather than in TODO file?

Some systems failed to build for Quicklisp dist

Building with SBCL 2.1.10 / ASDF 3.3.5 for quicklisp dist creation.

Trying to build commit id ac2e006

lil fails to build with the following error:

; caught WARNING:
;   The function COMPARE is called with four arguments, but wants exactly three.
...
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001C08103}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "lil/pure/lexicographic" "file-type">

lil/test fails to build with the following error:

; caught WARNING:
;   The function COMPARE is called with four arguments, but wants exactly three.
...
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001C08103}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "lil/pure/lexicographic" "file-type">

lisp-interface-library fails to build with the following error:

; caught WARNING:
;   The function COMPARE is called with four arguments, but wants exactly three.
...
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING {1001C08103}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "lil/pure/lexicographic" "file-type">

Full log here

Some systems failed to build for Quicklisp dist

Building with SBCL 2.3.6.173-55d27b14b / ASDF 3.3.5 for quicklisp dist creation.

Trying to build commit id ac2e006

lil fails to build with the following error:

; caught WARNING:
;   The function COMPARE is called with four arguments, but wants exactly three.
...
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD tid=1290945 "main thread" RUNNING {1001710003}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "lil/pure/lexicographic" "file-type">

lil/test fails to build with the following error:

; caught WARNING:
;   The function COMPARE is called with four arguments, but wants exactly three.
...
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD tid=1290941 "main thread" RUNNING {1001710003}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "lil/pure/lexicographic" "file-type">

lisp-interface-library fails to build with the following error:

; caught WARNING:
;   The function COMPARE is called with four arguments, but wants exactly three.
...
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD tid=1290949 "main thread" RUNNING {1001710003}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "lil/pure/lexicographic" "file-type">

Full log here

Add stateful sets.

Currently there are pure sets, and there are set interfaces defined in lil/interface/set that say they are for both pure and stateful, but it doesn't look like there are any stateful sets defined.

Using <classy>

I have a short question regarding how the interface is supposed to be implemented. I usually define my interfaces in two files. Say some interface in file car.lisp with implementation in car-implementation.lisp. I want to have the interface bound to the class car which I have until now typically defined in car.lisp. On compiling I get an error that the class is not defined yet. I could move the class definition to a third file (in car-implementation.lisp causes circularity) but this seems a bit superfluous. Any ideas? Also would it not make sense to implement as parametric. One could then bind it to a variable and include it in the superinterface list as a mixin of sorts.

Some systems failed to build for Quicklisp dist

Building with SBCL 2.3.6.173-55d27b14b / ASDF 3.3.5 for quicklisp dist creation.

Trying to build commit id 9b8f3cf

lil fails to build with the following error:

; caught WARNING:
;   The function EMPTY is called with two arguments, but wants exactly one.
...
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD tid=2323792 "main thread" RUNNING {1001710003}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "lil/transform/linearized-map" "file-type">

lil/test fails to build with the following error:

; caught WARNING:
;   The function EMPTY is called with two arguments, but wants exactly one.
...
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD tid=2323788 "main thread" RUNNING {1001710003}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "lil/transform/linearized-map" "file-type">

lisp-interface-library fails to build with the following error:

; caught WARNING:
;   The function EMPTY is called with two arguments, but wants exactly one.
...
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD tid=2323796 "main thread" RUNNING {1001710003}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "lil/transform/linearized-map" "file-type">

Full log here

Metadata for Quicklisp

Please consider adding :description, :author and :license information to your ASDF system(s). This will greatly help Quicklisp users and make it easier for them to report bugs.

More information:

http://blog.quicklisp.org/2015/05/looking-for-more-metadata.html
https://www.quicklisp.org

fare / lisp-interface-library Goto Github PK

lisp-interface-library's Introduction

lisp-interface-library

Features

Building it

Using it

lisp-interface-library's People

Contributors

Stargazers

Watchers

Forkers

lisp-interface-library's Issues

Recommend Projects

Recommend Topics

Recommend Org