[CfP] 4th European Lisp Symposium, Hamburg, March 31 - April 1st, 2011

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

		     4th European Lisp Symposium
	      Special Focus on Parallelism & Efficiency

		      March 31 - April 1st, 2011
		TUHH, Hamburg University of Technology
			   Hamburg, Germany

	       http://www.european-lisp-symposium.org/

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Important Dates
~~~~~~~~~~~~~~~~
+ Submission Deadline: January  09, 2011
+ Author Notification: February 06, 2011
+ Final Paper Due:     February 28, 2011
+ Symposium:           March 31 - April 1st, 2011

Authors of accepted research contributions will be invited to submit
an extended version of their papers for journal publication.

Scope
~~~~~~
The purpose of the European Lisp Symposium is to provide a forum for
the discussion and dissemination of all aspects of design,
implementation and application of any of the Lisp dialects, including
Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure,

CCL upgrading issues

Hello:

   I wish I could give more details on this bug, but I'm having a hard  
time isolating it.  Maybe the following explanation will trigger an  
"oh, that's easy" reaction
in one of you.

   I've been trying to upgrade from CCL 1.1 to 1.4, but I run into a  
problem in 1.4.  It could easily be something that happens in 1.1 as  
well (and I just don't get the nice
error messages in 1.1), but I seem to be able to do longer (at least)  
runs in 1.1 before any melt-downs occur.

   I'm drawing a lot of graphics windows, some with simple x-y plots  
and some with more detailed cell grids (with each cell being a  
different color).  So there's a lot of
drawing going on.  Although I first thought that the crashes were due  
to the cell-grid plots, it now just seems like I get the crash after  
"a bit" of plotting.  Sometimes the
crash comes after 5 or 6 windows.  Sometimes I get 15 or 20 up there  
before everything hangs, but it does seem like the probability of a  
crash increases with the
number of cell grids that I draw.

   The error message is normally the same: a nil macptr in a call to  
drawRect.

Here's a live specimen:

   > Error: value NIL is not of the expected type MACPTR.

? cffi

good morning;

has anyone ported cffi to mcl?

_______________________________________________
info-mcl mailing list
info-mcl@...
http://clozure.com/mailman/listinfo/info-mcl

Re: ? cffi

Never know how to do FFI in Digitool MCL ... Where can I find some API documents?

--binghe

在 2010-9-22，05:36， james anderson 写道：

> good morning;
> 
> has anyone ported cffi to mcl?
> 
> 
> _______________________________________________
> info-mcl mailing list
> info-mcl@...
> http://clozure.com/mailman/listinfo/info-mcl

_______________________________________________
info-mcl mailing list
info-mcl@...
http://clozure.com/mailman/listinfo/info-mcl

Re: ? cffi

there are two sources.

if you go to ftp.clozure.com, you will find the 5.2 release and a  
copy of the documentation for 4.0.
i know of no revised documentation for 5.2. other than that, there is  
always the source.
i believe 5.2 has a very different calling mechanism then 4.0, as it  
uses a different os x facility to manage foreign libraries.

the biggest '?' is turning off the gc for the dynamic extent of any  
foreign calls which pass lisp data. i do not know if that is possible  
in mcl, but it could be faked by moving the data to/from temporary  
external storage just to get it working.
two little question marks are the data type size calculations and the  
call-back protocol.
since the source is there, there's nothing stopping me from adapting  
the clozure-specific code to work in mcl.
i was just hoping to avoid having to wrap my head around those bits.

On 2010-09-22, at 04:45 , Chun Tian (binghe) wrote:

> Never know how to do FFI in Digitool MCL ... Where can I find some  
> API documents?
>
> --binghe
>
> 在 2010-9-22，05:36， james anderson 写道：
>
>> good morning;
>>

Re: ? cffi

I've read these documents. MCL 4.0's FFI seems based on the function "define-entry-point" which then
depends on "ppc-ff-call", both of them are still available in MCL 5.x, and the related MCL source code is
"lib/deftrap.lisp", which was last modified in 2005.

However, I think "define-entry-point" is not the preferred way any more:

; Change log
;
; put back define-entry-point and things it depends on - though MCL doesn't use it users may
; ------ 5.2b2

I think CFFI people, if want to support MCL, should research "deftrap.lisp" and figure out the preferred
way to do the work. But for me, a USOCKET maintainer, I'd like to use this interface directly to implement
UDP networking, which was lack from OpenTransport.

--binghe

在 2010-9-22，13:30， james anderson 写道：

> there are two sources.
> 
> if you go to ftp.clozure.com, you will find the 5.2 release and a copy of the documentation for 4.0.
> i know of no revised documentation for 5.2. other than that, there is always the source.
> i believe 5.2 has a very different calling mechanism then 4.0, as it uses a different os x facility to manage
foreign libraries.
> 
> the biggest '?' is turning off the gc for the dynamic extent of any foreign calls which pass lisp data. i do
not know if that is possible in mcl, but it could be faked by moving the data to/from temporary external
storage just to get it working.
> two little question marks are the data type size calculations and the call-back protocol.

Re: ? cffi

good morning;

i have worked out enough of a cffi-mcl to be able to accomplish the  
immediate goal - to use the cl-zmq zeromq ffi binding.[1]
in case someone wants to carry it further, it's posted along with a  
mcl-compatible zmq version,[2] which eliminates un-ported dependencies.

---
[1] : http://repo.or.cz/w/cl-zmq.git
[2] : http://github.com/lisp/de.setf.zeromq

On 2010-09-22, at 08:29 , Chun Tian (binghe) wrote:

> I've read these documents. MCL 4.0's FFI seems based on the  
> function "define-entry-point" which then depends on "ppc-ff-call",  
> both of them are still available in MCL 5.x, and the related MCL  
> source code is "lib/deftrap.lisp", which was last modified in 2005.
>
> However, I think "define-entry-point" is not the preferred way any  
> more:
>
> ; Change log
> ;
> ; put back define-entry-point and things it depends on - though MCL  
> doesn't use it users may
> ; ------ 5.2b2
>
> I think CFFI people, if want to support MCL, should research  
> "deftrap.lisp" and figure out the preferred way to do the work. But  
> for me, a USOCKET maintainer, I'd like to use this interface