Re: LISP module from CPAN
On Mon, May 07, 2007 at 08:39:28PM +0400, Vadim wrote: Adam Kennedy wrote: One alternative for the bridging stuff would be to look at using something like Language::LISP. ... That tends to be a more common area for bridges to languages. Although there are different approaches within Language:: namespace (bridge connections like Language::Haskell, etc, and also toy implementations like Language::Basic) it is indeed common area for bridges to languages. So, I'll stick with Language::Lisp name. If your module only connects to one LISP implementation, I'd urge you to make sure you put that name in the namespace, eg Language::Lisp::CMUCL. -- Benjamin Smith [EMAIL PROTECTED]
Re: LISP module from CPAN
Benjamin Smith wrote: On Mon, May 07, 2007 at 08:39:28PM +0400, Vadim wrote: Adam Kennedy wrote: One alternative for the bridging stuff would be to look at using something like Language::LISP. ... That tends to be a more common area for bridges to languages. Although there are different approaches within Language:: namespace (bridge connections like Language::Haskell, etc, and also toy implementations like Language::Basic) it is indeed common area for bridges to languages. So, I'll stick with Language::Lisp name. If your module only connects to one LISP implementation, I'd urge you to make sure you put that name in the namespace, eg Language::Lisp::CMUCL. no, it uses CFFI, so this should cover every implementation supporting that. I'm developing using CLISP, but not relying on its internals. Indeed, implementation-dependant things should be in their own packages. Vadim.
Re: In which linux distribution is my module available
Adam Kennedy wrote: FreeBSD is auto-packaging everything that passes tests. Not entirely true. FreeBSD ports are added and maintained by hand, by a group of volunteers. /Lars
Re: How to name module for CPAN for common lisp connection
could your approach be made to work with the Inline:: framework? On 5/6/07, Vadim Konovalov [EMAIL PROTECTED] wrote: I want to publish perl-to-lisp bridge module to CPAN. It connects existing LISP implementation to Perl, which turns out to be robust LISP out from perl (as opposed to toy implementations).
Re: LISP module from CPAN
On 5/8/07, Vadim [EMAIL PROTECTED] wrote: no, it uses CFFI, so this should cover every implementation supporting that. Ever since reading Hackers and Painters http://www.amazon.com/exec/obidos/ISBN=0596006624/tipjartransactioA I've been defending Perl is a LISP! (which is actually quite easy, because nobody knows what I'm talking about) Are there a lot of libraries and things written to CFFI? Perl could provide a CFFI interface, that would strengthen the perl is a lisp meme.
Re: LISP module from CPAN
David Nicol wrote: On 5/8/07, Vadim [EMAIL PROTECTED] wrote: no, it uses CFFI, so this should cover every implementation supporting that. Ever since reading Hackers and Painters http://www.amazon.com/exec/obidos/ISBN=0596006624/tipjartransactioA I've been defending Perl is a LISP! (which is actually quite easy, because nobody knows what I'm talking about) Are there a lot of libraries and things written to CFFI? Perl could provide a CFFI interface, that would strengthen the perl is a lisp meme. I'm not CFFI expert, so can't really comment. Looking at CFFI homepage at http://common-lisp.net/project/cffi/ this gives me an idea this is a LISP-only beastie... But, given SWIG provides support of CFFI, may be its already not so far distant from Perl... (answering to your other question) No, Inline:: approach is very different.. PS. I'll upload very first very unperfect version of Language::Lisp module to CPAN later today. Vadim.
Re: LISP module from CPAN
Hi, all, PS. I'll upload very first very unperfect version of Language::Lisp module to CPAN later today. finally I did it. the module is very small but it allows to tie together these three things: Perl, Lisp and, for example, Tcl/Tk, thus allowing to use tight integration of LISP-based CAS system (Maxima, axiom, etc) and use GUI w/o sockets, directly from Perl. Best regards, Vadim.
