Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Easy-ISLisp update and open source

157 views
Skip to first unread message

ken...@gmail.com

unread,
Feb 2, 2019, 9:00:53 PM2/2/19
to
Dear everyone.

I updated the Easy-ISLisp(EISL) that is compatible with ISLisp standard.
Also, I made it open source.
https://github.com/sasagawa888/eisl

Kenichi Sasagawa

Eugene Zaikonnikov

unread,
Feb 4, 2019, 6:04:17 PM2/4/19
to


So very unusual, thanks for sharing!

--
Eugene

ken...@gmail.com

unread,
Feb 4, 2019, 8:09:40 PM2/4/19
to
Hi Eugene.

Thank you for having interest.

Kenichi Sasagawa

Steve Graham

unread,
Feb 7, 2019, 1:27:20 AM2/7/19
to
How is it different from Common Lisp?

Steve

christia...@novasparks.com

unread,
Feb 7, 2019, 2:30:23 AM2/7/19
to
On Thursday, February 7, 2019 at 7:27:20 AM UTC+1, Steve Graham wrote:
> How is it different from Common Lisp?
ISLISP, on which Easy-ISLisp is based on, is an ISO standard (see: https://en.wikipedia.org/wiki/ISLISP)

At first glance, you can view ISLISP as a minimal yet complete subset of CommonLisp. Standard is nearly 10x smaller than CLtL.

It has about the same special forms, same semantic, and ILOS, its OOP, cab be view as the core of CLOS.

It has been proved that ISLISP can reside in a CLtL package (it was a goal of ISLISP spec.).

At the opposite, ISLISP has all the material to implement CLtL missing features.
OpenLisp (https://en.wikipedia.org/wiki/OpenLisp), a pure ISLISP based interpreter/compiler, has most of CLtL features.

C.

Steve Graham

unread,
Feb 7, 2019, 5:10:02 PM2/7/19
to
Thanks, Christian.

Why would one choose ISLisp over Common Lisp?

Steve

eli...@gmail.com

unread,
Feb 8, 2019, 2:33:43 AM2/8/19
to
> Why would one choose ISLisp over Common Lisp?

When we started to normalize ISLISP back in 1987, ANSI CLtL was also an important effort to normalize (another) Lisp. If ever ISLISP won, CLtL guys would not be out of the train. We worked hard to ensure ISLISP had no semantic incompatibilities and that the few differences could be implemented easily in CLtL. I remember that an :islisp CLtL package has been made by s.o. (can't remember who, maybe Kent Pitman?) to prove that CLtL can be the implementation language of pure ISLISP.

With this package, CLtL implementations could claim that they are also ISO/IEC 13816:1997(E) compatible.

Steve Graham

unread,
Feb 8, 2019, 10:52:02 AM2/8/19
to
Thanks for the explanation.
0 new messages