Re: static-vectors

Hello clisp-list@ - a brief update from me on my original post.

On Sun, Aug 26, 2018 at 11:40 AM, edgar <[email protected]> wrote:

> Am Sun, 26 Aug 2018 09:04:57 +0100
> schrieb C Habs <[email protected]>:
>
> > Hello clisp-list
> >
> > I may be going over something already mentioned - apologies if so.
> >
> > From trying to 'install'  Woo  using Quicklisp, there was displayed
> > the following message:
> >
> > quicklisp/software/static-vectors-v1.8.3/static-vectors.asd:
> >       static-vectors does not support this Common Lisp implementation!
> >
> >
> > Please excuse my ignorance; what is a 'static vector' and why is this
> > a problem in CLISP and can it be that CLISP could support
> > static-vector ?
>
> The "Requirements" section on https://github.com/fukamachi/woo
> says that "Woo" currently
> * runs on no other operating system than Linux
> * runs on no other Common Lisp implementation than SBCL
> * requires libev to be installed
>
> Tracking down the dependencies, woo.asd
> https://github.com/fukamachi/woo/blob/master/woo.asd
> requires static-vectors and static-vectors.asd
> https://github.com/sionescu/static-vectors/blob/master/static-vectors.asd
> says that it runs on Franz Allegro, CCL, CMUCL, ECL, Lispworks, and
> SBCL, while all other Common Lisp implementations ar not supported
>
> > As an aside (or not), being new to *Common Lisp*, I find it
> > frustrating at times that there are many lisps and not all are equal;
> > this results in some applications only working with certain lisps and
> > things not being so common :-) .  I'm sure there will be some defence
> > to this situation, but none the less, it can be a challenge to a
> > newbie.
>
> Woo is obviously a non-comforming Common Lisp program
> but fails to say so on the GitHub page.
>
> Conforming Common Lisp programs should run on *all*
> Common Lisp implementations, not only on SBCL.
>
> - edgar
>



Just for information rather than any thing else at the moment, I wrote to
the maintainer of the 'static-vectors' out of interest and not
unsurprisingly [for me], I got this informative reply:

"...


It has been suggested to me by replies to a question I raised to
'clisp-list'  mailing list, to make contact to request an enhancement to
'static-vectors' that enables it to work with GNU CLISP lisp (on linux of
course).

Bearing in mind I am new to lisp and therefore I have no idea why not all
lisps are seen as equal and why some applications/libraries are not built
to *common lisp* and therefore do not work on all *common lisp* compliant
lisps (which I think ought to be the desire to have common lisp compliance
and universal use):-


The standardized Common Lisp is not enough for many purposes, first of all
it lacks a FFI and networking; therefore all programs that need that rely
on non-standard extensions.

- please can you comment if there is something fundamentally lacking with
CLISP that results currently in the message, during attempting installation
via Quicklisp, that it will not work with the CLISP implementation of
*common lisp*  ?


Clisp is almost unmaintained and I - as well as most Lisp developers I know
- simply don't use it and don't port our libraries to Clisp. I'm happy to
accept patches to static-vectors that adds Clisp support but I'm not
interested in doing any work on that.


...."



As new to Lisp/CLISP, as I said alluded to previously, this sort of
perception seems to crop up more than perhaps it should for *common lisp*
CLISP.  I like CLISP too (it shipped by default with my preference of Linux
distro :-)  .  It is a real shame if people are developing things but
perceive common lisp as lacking and therefore their offerings are for some
extended common lisp that results in more exclusivity than the common.   I
ramble, but there you go.



Regards and best wishes
Habs
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list