Re: static-vectors
C Habs <[email protected]> Fri, 31 Aug 2018 20:13:40 +0100
| Newsgroups | gmane.lisp.clisp.general |
|---|---|
| Message-ID | <CANe8y8ZPxZo7L1pfw5g44M1afeDKNRMnR8g=cDwvD+9A_dA6Aw@mail.gmail.com> |
Hello to you Jean Louis On Fri, Aug 31, 2018 at 7:57 PM, Jean Louis <[email protected]> wrote: > Hello Herr Habs, > > Just using 'Habs' for me is fine. :-) Thank you for the comments. Yes, I understand. > > However, if you are beginner in LISP then why not > use some other web server solution but woo? > > I am aware of other servers, but I was asking the learned on here about a particular point of some applications/libraries not working with all *common* lisps and I now am better informed :-) > Maybe somebody on this list can help to make > static-vectors work on CLISP. > > > > > Woo is obviously a non-comforming Common Lisp program > > > but fails to say so on the GitHub page. > > Yes, I find that also stupid, and I do not find it > "Common Lisp program" as long as it is not > "common" and cannot be used within other > conforming implementations of Common Lisp. > > > > Conforming Common Lisp programs should run on *all* > > > Common Lisp implementations, not only on SBCL. > > Absolutely yes, I agree. > > That happens because some of authors focus only on > one implementation. > > > 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. > > That may be, I am not a specialist, but I know > that CLISP does have option for FFI, however maybe > the author of static-vectors did not look enough > into CLISP to make it work. > > > 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. > > Well I cannot agree on that, and it means > nothing. Obviously CLISP is under development and > what needs to be maintained if it is already well > conforming Common Lisp implementation? > > So the statement like that is not specific. It > just means that the author did not look enough > into his own authorship, and he even said so. > > > 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. > > Yes those things happen. > > However, what exactly do you try to accomplish? > Again, I don't think I am seeking help for some solution (though that would be nice re: static-vectors; I will have a look myself for what it is worth regarding my ability); as explained above, it was more of finding out/receiving comments on what many 'lispers' probably have already come across. > I am using CLISP as CGI program, and it is already > very good and fast that way, it is compiled and > does what I want. > > And I am using it under Nginx webserver. > > -- > Jean Louis > All the above said and done, I am quietly enjoying CLISP lisp and I wish so much I had been exposed to it much earlier :-) Regards to all. 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