- eurolisp - mailman3.common-lisp.net

[eurolisp] Web Application Frameworks in Smalltalk and Common Lisp
by Pascal Costanza 21 Apr '05

21 Apr '05

Web application frameworks in Smalltalk and Common Lisp ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Monday, 25th of April 2005, Vrije Universiteit Brussel http://prog.vub.ac.be/events/2005/BADL/WebApplicationFrameworks.html The VUB (Programming Technology Lab), ULB (deComp), Belgian Assocation for Dynamic Languages (BADL) and the Belgian Smalltalk User Group (BSUG) are very pleased to invite you to two presentations about web application frameworks based on Smalltalk and Common Lisp. The two presenters are the main authors of the respective frameworks and will show you first-hand overviews and illustrate examples from, and experiences with, real-world use scenarios. It will be especially interesting to see what advantages the use of non mainstream dynamic programming languages brings to the table in a domain that is specifically targeted by Java and .NET frameworks. We also expect a heated discussion about the merits of the use of continuations in Seaside and the lack thereof in the Fractal Framework. ;) The schedule for this event, held on Monday 25th of April, is as follows: - 15:00 - 16:00 Avi Bryant, Seaside - 16:00 - 17:00 Marc Battyani, Fractal Framework - 17:00 - 18:00 Open Podium Discussion This event is rounded out with a little reception. The venue for the event is the Vrije Universiteit Brussel, Campus Etterbeek, Pleinlaan 2, 1050 Brussels, Belgium. For a description of how to get there see http://www.vub.ac.be/english/campEt.html The exact location is still to be determined and will be announced at the following website: http://prog.vub.ac.be/events/2005/BADL/WebApplicationFrameworks.html Please make sure to register for the event at the website, so we can plan ahead. The number of places will be limited according to the exact location of the event, and will be announced at the website. Below are the abstracts of the presentations and the biographies of the speakers. Avi Bryant, Seaside +++++++++++++++++++ On the web, abstraction is a dirty word. The dominant paradigms and philosophies of web development -- CGI, Servlets, Server Pages, REST -- provide only a thin wrapper around the low-level details of HTTP, and encourage you to use the rough stones of the transport protocol as the direct building blocks of your application. Web developers by and large reject any further abstraction in the way that assembly hackers once rejected structured programming: it's too inflexible, uses too many resources, and above all, it doesn't let you see what's *really* going on. As a result, web applications suffer the same problems now that assembly language programs did years ago; they're fragile, verbose, difficult to maintain and ill-suited to reuse. That's not to say that better abstractions aren't available. The Lisp and Scheme communities have been working on them for years. Paul Graham's ViaWeb pioneered the use of closures, not query parameters, to capture application state in each link. Christian Quiennec showed how to use first class continuations to invert the flow of control of HTTP and put the server back in the driver's seat. Macro packages like htmlgen bring HTML into the language itself, opening up much more than a template system can provide. Meanwhile, object-oriented packages like WebObjects have demonstrated how to decompose the web page into a tree of stateful, interacting objects, allowing a finer granularity of development. Seaside combines these ideas and others with the rich development environment of Smalltalk to provide a stable, complete, and innovative web application platform. This talk will introduce Seaside, and will focus in particular on the ways in which these abstractions can be leveraged to enable reuse: how to use closures, continuations, and intelligent HTML generation to destroy the intra- and inter-page coupling that is holding web development back. Marc Battyani, Fractal Framework ++++++++++++++++++++++++++++++++ Web sites have evolved from static documents to simple applications (eCommerce) and now to complete applications. Today, frameworks like J2EE and .Net are used for writing these applications made of tens to hundreds of object classes. These huge frameworks suffer from the limitations of their programming languages. Other frameworks, based on continuations, are emerging but still have limitations for complex applications. The Framework presented here has been used in production since 2001 and shows how the unique qualities of Common Lisp can boost the productivity by more than an order of magnitude for writing web applications compared to J2EE/.Net. This framework automatically generates the presentation, modification, validation, storage and data integrity layers of all the object classes of an application. It provides session management, web controls and a unique way for collaborative work. Internally, it makes extensive use of the Meta Object Protocol, CLOS generic functions, lexical closures, and on the fly code generation and compilation. The speakers ++++++++++++ Avi Bryant is the co-founder of Smallthought Systems Inc. Much of his work centers around the use of Squeak Smalltalk as a platform for commercial software development. As an actively contributing member of the Squeak community, he maintains its standard version control system, as well as packages for web development and relational and object database access. As a consultant, he has helped companies develop Squeak-based products for the travel, theatre, and finance industries, higher education, and mobile devices. Avi is based in Vancouver, Canada but currently residing in The Netherlands. Marc Battyani's professional activities involve electronics design and writing software. He is the founder of Fractal Concept and the author of several open-source libraries (mod_lisp, cl-pdf, cl-typesetting). He works on various domains ranging from medical or industrial systems and applications to network infrastructure management web applications for banks as well as 3D software for robotized testing equipment, 6D real time positioning systems for the industry and the military, smart environmental radio sensors, etc. All the application software is written in Common Lisp with Fractal Concept's web application framework. Marc has a MSc in electronics and a MSc in computer science. He lives near Fontainebleau in France.

5 12

[eurolisp] European Common Lisp meeting - cancellation
by Andreas Thiele 21 Apr '05

21 Apr '05

Dear Lispers, unfortunately I have to cancel the meeting. Perhaps there is somebody else who wants to take my seet? Andreas

1 0

[eurolisp] Fwd: CFP: DLS05: ACM Dynamic Languages Symposium
by Pascal Costanza 19 Apr '05

19 Apr '05

This is probably very interesting! Pascal Begin forwarded message: > From: Roel Wuyts <Roel.Wuyts(a)ulb.ac.be> > Date: 17 April 2005 10:51:17 GMT+02:00 > To: ecoop-info(a)ecoop.org > Subject: CFP: DLS05: ACM Dynamic Languages Symposium > > CALL FOR PAPERS FOR THE > > ACM Dynamic Languages Symposium 2005 > October 18, 2005 > San Diego, California > (co-located with OOPSLA'05) > > URL: http://decomp.ulb.ac.be:8082/events/dls05/ > > ----------- > Abstract > ----------- > > In industry, static languages (such as Java, C++ and C#) are much more > widely used than their dynamic counterparts (like CLOS, Python, Self, > Perl, php or Smalltalk). So it appears as though dynamic language > concepts were forgotten and lost the race. > > But this is not the case. > > Java and C#, the latest mainstream static languages, popularized to a > certain extent dynamic language features such as garbage collection, > portability and (limited forms of) reflection. In the near future, we > expect this dynamicity to increase even further. E.g., it is getting > clearer year after year that pervasive computing is becoming the rule > and that concepts such as meta programming, reflection, mobility, > dynamic reconfigurability and distribution are becoming increasingly > popular. All of these features are the domain of dynamic languages, > and hence it is only logical that more dynamic language concepts have > to be taken up by static languages, or that dynamic languages can make > a breakthrough. > > Currently, the dynamic language community is fragmented, split over a > multitude of paradigms (from functional over logic to > object-oriented), languages and syntaxes. This fragmentation severely > hinders research as well as acceptance, and results in either language > wars or, even worse, language ignorance. The goal of this symposium is > to provide a highly visible, international forum for researchers > working on dynamic features and languages. We explicitly invite > submissions from all kinds of paradigms (object-oriented, functional, > logic, ...), as can be seen >> from the structure of the program committee. > > Areas of interests include, but are not limited to: > - closures > - delegation > - actors, active objects > - constraint systems > - mixins and traits > - reflection and meta-programming > - language symbiosis and multi-paradigm languages > - experience reports on successful application of dynamic languages > > Accepted Papers will be published in the ACM Digital Library. > > > ------------------------------- > Submission Guidelines > ------------------------------- > > Papers will need to be submitted using an online tracking system, of > which the URL will be given later. > > All papers must be submitted electronically in PDF format (or > PostScript, if you do not have access to PDF-producing programs, but > this is not recommended). Submissions, as well as final versions, must > be formatted to conform to ACM Proceedings requirements: Nine point > font on ten point baseline, two columns per page, each column 3.33 > inches wide by 9 inches tall, with a column gutter of 0.33 inches, > etc. See the ACM Proceedings Guidelines. You can save preparation time > by using one of the templates from that page. Note that MS Word > documents must be converted to PDF before being submitted. > > ---------------------- > Important Dates > ---------------------- > > - Deadline for receipt of submissions: June 24th 2005 > - Notification of acceptance or rejection: August 5th 2005 > - Final version for the proceedings: To be announced later > > --------------------------- > Program Committee > --------------------------- > > - Gilad Bracha > - Wolfgang De Meuter > - Stephane Ducasse > - Gopal Gupta > - Robert Hirschfeld > - Dan Ingalls > - Yukihiro Matsumoto > - Mark Miller > - Eliot Miranda > - Philippe Mougin > - Oscar Nierstrasz > - Dave Thomas > - David Ungar > - Guido Van Rossum > - Peter Van Roy > - Jon L White (G) > - Roel Wuyts (Chair) > > > -- > Roel Wuyts > DeComp > roel.wuyts(a)ulb.ac.be Université Libre de > Bruxelles > http://homepages.ulb.ac.be/~rowuyts/ > Belgique > Vice-President of the European Smalltalk Users Group: www.esug.org > -- 2nd European Lisp and Scheme Workshop July 26 - Glasgow, Scotland - co-located with ECOOP 2005 http://lisp-ecoop05.bknr.net/

1 0

[eurolisp] Who will go to ILC05 at Stanford?
by Ernst van Waning 14 Apr '05

14 Apr '05

Hello, As you will have noticed, ALU will organize ILC05 next June at Stanford university (http://www.alu.org/alu/ilc05-registration.html) As we think of organizing the next ILC in Europe, we would like to know who will go to Stanford, so we can start preliminary discussions about the organization. Can you reply to me? Kind regards, Ernst van Waning President, ALU

1 0

[eurolisp] Amsterdam, Amsterdam!
by Pascal Costanza 08 Apr '05

08 Apr '05

Hi everybody, I am fixing my plans for the Amsterdam trip (no drugs, just Lisp ;). Can anyone recommend a good and cheap hotel? Thanks, Pascal -- 2nd European Lisp and Scheme Workshop July 26 - Glasgow, Scotland - co-located with ECOOP 2005 http://lisp-ecoop05.bknr.net/

10 21

[eurolisp] [ANN] Closer to MOP
by Pascal Costanza 03 Apr '05

03 Apr '05

Hi, I have just made the first public release of Closer to MOP available, a compatibility layer for a number of Common Lisp / CLOS implementations that bring their MOPs closer to the AMOP specification. Supported Common Lisp implementations include Allegro Common Lisp 6.2 Trial Version, CLisp (current CVS builds), CMUCL 19a+ (experimental Darwin port), LispWorks for Macintosh 4.3 Personal Edition, OpenMCL 0.14.3 and SBCL 0.8.21. All tests have been performed under Mac OS X 10.3.8. See a list of the fixed features below. This release is accompanied by v0.1 of the MOP Feature Tests on which Closer to MOP is based. Please note that the software is in an early stage and requires a good understanding of the CLOS MOP and its specification as found in AMOP. Further note that the feature tests and the fixes provided by Closer to MOP are not complete. Please carefully check the documentation provided with the above libraries. The software can be downloaded from http://common-lisp.net/project/closer/ Cheers, Pascal Features that don't adhere to AMOP in various CLOS MOP implementations, and whether and how they are resolved in Closer to MOP. (Note: This list may include mistakes and misinterpretations of the AMOP specification!) Allegro Common Lisp, 6.2 Trial edition - COMPUTE-DEFAULT-INITARGS takes more parameters than specified. Not fixed. Conditionalize on #+allegro for your own methods instead. - DEFGENERIC does not call FIND-METHOD-COMBINATION. Not fixed. - DEFMETHOD doesn't call MAKE-METHOD-LAMBDA. Not fixed. - The dependent protocol for generic functions doesn't work fully. Fixed. - The function invocation protocol doesn't call COMPUTE-APPLICABLE-METHODS, COMPUTE-APPLICABLE-METHODS-USING-CLASSES and COMPUTE-EFFECTIVE-METHOD. Not fixed. - MAKE-METHOD-LAMBDA is not provided. Not fixed. - Method functions don't take parameters as specified in AMOP, but instead just the parameters that the generic function receives. Not fixed. - REINITIALIZE-INSTANCE doesn't determine a new discriminating function. Fixed. - (SETF CLASS-NAME) and (SETF GENERIC-FUNCTION-NAME) do not use REINITIALIZE-INSTANCE for changing the names. Fixed. - VALIDATE-SUPERCLASS doesn't recognize T as a valid superclass. Not fixed. CLisp, 2.33.x None of the incompatibilities in CLisp are fixed. - Methods are not initialized with :function. - ADD-METHOD, REMOVE-METHOD, INITIALIZE-INSTANCE and REINITIALIZE-INSTANCE do not determine a new discriminating function. This is postponed until function invocation instead, so shouldn't be a problem in practice. - DEFGENERIC does not call ENSURE-GENERIC-FUNCTION-USING-CLASS. (I don't see how one can usefully specialize E-G-F-U-C anyway.) - DEFMETHOD does not call ADD-METHOD and MAKE-METHOD-LAMBDA. - A FORWARD-REFERENCED-CLASS is not changed via CHANGE-CLASS (but is correctly reinitialized via REINITIALIZE-INSTANCE). - MAKE-METHOD-LAMBDA is not provided. CMUCL, 19a+ Darwin/Exp 2004-07-25-090 - Accessor methods are not initialized with :function, :lambda-list, :slot-definition and :specializers. Fixed. - Classes cannot be anonymous. Fixed. - Class initialization doesn't call READER-METHOD-CLASS and WRITER-METHOD-CLASS for accessor methods. Fixed. - DEFMETHOD does not call MAKE-METHOD-LAMBDA. Not fixed. - The dependent protocol for generic functions doesn't work fully. Fixed. - Effective slot definitions are not initialized with :documentation, and EFFECTIVE-SLOT-DEFINITION-CLASS also doesn't receive that initarg. Not fixed. - Methods are not initialized with :function. Not fixed. - Multiple slot options are not passed as lists to DIRECT-SLOT-DEFINITION-CLASS. Not fixed, but use FIX-SLOT-INITARGS as a workaround. - REINITIALIZE-INSTANCE doesn't determine a new discriminating function. Fixed. - (SETF CLASS-NAME) and (SETF GENERIC-FUNCTION-NAME) do not use REINITIALIZE-INSTANCE for changing the names. Fixed. - STANDARD-CLASS and FUNCALLABLE-STANDARD-CLASS are not compatible. Not fixed. LispWorks, 4.3 Personal Edition - Accessor methods are not initialized with :function, :lambda-list, :slot-definition and :specializers. Fixed. - ACCESSOR-METHOD-SLOT-DEFINITION doesn't exist. Fixed. - ADD-METHOD doesn't call ADD-DIRECT-METHOD and REMOVE-METHOD. Fixed. - ADD-METHOD, REMOVE-METHOD, INITIALIZE-INSTANCE and REINITIALIZE-INSTANCE do not determine a new discriminating function. This is postponed until function invocation instead, so shouldn't be a problem in practice. - Effective slot definitions are not initialized with :allocation, and EFFECTIVE-SLOT-DEFINITION-CLASS also doesn't receive that initarg. Not fixed. This information is encoded in the initarg :flags, but I don't have any detailed information about that parameter. - Class initialization doesn't call READER-METHOD-CLASS and WRITER-METHOD-CLASS for accessor methods. Fixed. - Classes are not initialized with :direct-default-initargs, but with :default-initargs. Conditionalize on #+lispworks to fix this. - Class reinitialization does not call REMOVE-DIRECT-SUBCLASS. Fixed. - COMPUTE-APPLICABLE-METHODS-USING-CLASSES doesn't exist. Not fixed. - COMPUTE-DEFAULT-INITARGS doesn't exist. Not fixed. - DEFGENERIC does not call FIND-METHOD-COMBINATION. Not fixed. - The dependent protocol for generic functions doesn't work fully. Fixed. - When classes are initialized, :direct-superclasses are by default not empty. Not fixed, but direct superclasses are automatically adjusted when you use the standard idiom for adding a new default superclass. - EQL-SPECIALIZER, EQL-SPECIALIZER-OBJECT and INTERN-EQL-SPECIALIZER don't exist. In LispWorks, eql specializers are lists not objects. I have provided EQL-SPECIALIZER as a type (not as a class) and EQL-SPECIALIZER-OBJECT and INTERN-EQL-SPECIALIZER to work on lists, and a class EQL-SPECIALIZER* and corresponding EQL-SPECIALIZER-OBJECT* and INTERN-EQL-SPECILAIZER* to soften the incompatibilities. - FIND-METHOD-COMBINATION doesn't exist. Fixed, but fixed version doesn't work with method combination options. - FUNCALLABLE-STANDARD-INSTANCE-ACCESS and STANDARD-INSTANCE-ACCESS don't exist. Not fixed. - The function invocation protocol doesn't call COMPUTE-APPLICABLE-METHODS and COMPUTE-APPLICABLE-METHODS-USING-CLASSES. Not fixed. - Generic functions are not initialized with :declarations, but with 'declare. Not fixed. Conditionalize on #+lispworks instead. - MAKE-METHOD-LAMBDA expects other parameters than specified. Fixed. - Method functions don't take parameters as specified in AMOP, but instead just the parameters that the generic function receives. Not fixed. - READER-METHOD-CLASS and WRITER-METHOD-CLASS don't exist. Fixed. - REMOVE-METHOD doesn't call REMOVE-DIRECT-METHOD. Fixed. - (SETF CLASS-NAME) and (SETF GENERIC-FUNCTION-NAME) do not use REINITIALIZE-INSTANCE for changing the names. Fixed. - The slot methods (SLOT-VALUE-USING-CLASS, etc.) are not specialized on effective slot definitions, but on slot names. Fixed. - The generated accessor methods don't use the slot methods for accessing slots. Fixed. (Don't use :optimize-slot-access to deoptimize slot access, or otherwise the fixed slot access protocol doesn't work anymore!) - SPECIALIZER doesn't exist. Not fixed. - SPECIALIZER-DIRECT-GENERIC-FUNCTIONS doesn't exist. Fixed. - STANDARD-CLASS and FUNCALLABLE-STANDARD-CLASS are not compatible. Not fixed. OpenMCL, 0.14.3 In OpenMCL, generic functions work completely differently than specified. The specific incompatibilities are not listed and are not fixed. - EQL-SPECIALIZER is not exported. Fixed. SBCL, 0.8.21 - Accessor methods are not initialized with :function, :lambda-list, :slot-definition and :specializers. Fixed. - Classes cannot be anonymous. Fixed. - Class initialization doesn't call READER-METHOD-CLASS and WRITER-METHOD-CLASS for accessor methods. Fixed. - DEFMETHOD does not call MAKE-METHOD-LAMBDA. Not fixed. - The dependent protocol for generic functions doesn't work fully. Fixed. - Effective slot definitions are not initialized with :documentation, and EFFECTIVE-SLOT-DEFINITION-CLASS also doesn't receive that initarg. Not fixed. - METAOBJECT doesn't exist. Not fixed. - Methods are not initialized with :function. Not fixed. - Multiple slot options are not passed as lists to DIRECT-SLOT-DEFINITION-CLASS. Not fixed, but use FIX-SLOT-INITARGS as a workaround. - REINITIALIZE-INSTANCE doesn't determine a new discriminating function. Fixed. - (SETF CLASS-NAME) and (SETF GENERIC-FUNCTION-NAME) do not use REINITIALIZE-INSTANCE for changing the names. Fixed. - STANDARD-CLASS and FUNCALLABLE-STANDARD-CLASS are not compatible. Not fixed. Summary: - If you specialize COMPUTE-DEFAULT-INITAGS, conditionalize for the extra parameters in Allegro Common Lisp. - Don't rely on FIND-METHOD-COMBINATION to do its job correctly, only when you don't provide method combination options. - MAKE-METHOD-LAMBDA only works in CMUCL and SBCL to a certain extent, and in LispWorks to a certain other extent. It CMUCL and SBCL, MAKE-METHOD-LAMBDA isn't called under certain circumstances, and in LispWorks, the returned lambda expression doesn't adhere to the AMOP specification. - Specialize the methods for the dependent protocol on the class or generic function metaobject class. The example in AMOP doesn't do this but that is fragile code. - Don't rely on methods being initialized with the specified initargs from inside the MOP. - CLisp doesn't change a FORWARD-REFERENCED-CLASS via CHANGE-CLASS. Apart from that, FORWARD-REFERENCED-CLASS works reliably across all MOPs. - Effective slot definitions and EFFECTIVE-SLOT-DEFINITION-CLASS don't receive :documentation in CMUCL and SBCL, and no :allocation (!) in LispWorks. - If you specialize DIRECT-SLOT-DEFINITION-CLASS, use FIX-SLOT-INITARGS in portable code. - In CMUCL, SBCL and LispWorks, STANDARD-CLASS and FUNCALLABLE-STANDARD-CLASS are not compatible. - The function invocation protocol only works in CMUCL, SBCL and CLisp. - If you need to see :direct-default-initargs when classes are initialized, conditionalize on #+lispworks to receive :default-initargs instead. - COMPUTE-DEFAULT-INITARGS doesn't exist (and isn't called) in LispWorks. - In LispWorks, eql specializers are lists. - FUNCALLABLE-STANDARD-INSTANCE-ACCESS and STANDARD-INSTANCE-ACCESS doesn't exist / should not be used in LispWorks. - If you need to see :declarations when generic functions are initialized, conditionalize on #+lispworks to receive 'declare instead. - In Allegro Common Lisp and LispWorks, method functions take the original parameters that a generic function has received. - In LispWorks, the class SPECIALIZER doesn't exist. - In SBCL, the class METAOBJECT doesn't exist. - If you need to rely on the generic function protocols, don't use MCL or OpenMCL (or be very careful - some minor things work there as specified). The following known problems with existing MOPs are not tested or fixed (yet): - Allegro: defmethod does not accept more than one qualifier. - SBCL/CMUCL (PCL): The object returned by compute-discriminating-function cannot be funcalled. - CLisp: A generic function without any method defined on it cannot be called. These problems may also occur in other CLOS implementations. ...end of transmission...

1 0

[eurolisp] [CfP] 2nd European Lisp & Scheme Workshop
by Pascal Costanza 30 Mar '05

30 Mar '05

+---------------------------------------------------------------------+ | 2nd European Lisp and Scheme Workshop | | July 26 - Glasgow, Scotland - co-located with ECOOP 2005 | | Supported by ALU | +---------------------------------------------------------------------+ *********************************************************************** Important - The workshop will include a keynote by Richard P. Gabriel. (pending) - We are looking for papers & for breakout group proposals! (see below) *********************************************************************** Important Dates: Submission deadline: May 16, 2005 Notification of acceptance: May 27, 2005 ECOOP early registration deadline: pending For more information visit http://lisp-ecoop05.bknr.net (expect a few updates in the near future) or contact pc(a)p-cos.net Organizers ********** Pascal Costanza, Programming Technology Lab, Vrije Universiteit Brussel Theo D'Hondt, Programming Technology Lab, Vrije Universiteit Brussel Arthur Lemmens, Independent Consultant, Amsterdam Manuel Serrano, INRIA Sophia-Antipolis, France Website: Hans Huebner, Berlin Overview ******** Lisp has a tradition of providing a fruitful basis for language design experiments for many decades. The structure of Lisp, including its current major dialects Common Lisp and Scheme, makes it easy to extend the language or even to implement entirely new dialects without starting from scratch. The Common Lisp Object System (CLOS) was the first object-oriented programming language to receive an ANSI standard. It is, arguably, the most complete and advanced object system of any language. Despite having somewhat disappeared from the radar of popular computer science, Lisp has just started to gain momentum again. There is a steadily growing interest in Lisp as such, with numerous user groups having formed recently worldwide, and Lisp's metaprogramming notions that are being transferred to other languages to different extents, as for example in AOP, MDA, DSL, and so on. This one-day workshop will address the near-future role of Lisp-based languages in research, industry and education. We want to solicit papers and suggestions for breakout groups that discuss the opportunities Lisp provides to capture and enhance the possibilities in software engineering. We also want to promote lively discussion between researchers proposing new approaches and practitioners reporting on their experience with the strengths and limitations of current Lisp technologies. Papers ****** Suggested Topics: * Macro programming * Metaprogramming * Reflection * New language features / abstractions * Case studies * Experience reports * Industrial applications * Object-Oriented Programming * Declarative Programming * Aspect-Oriented Programming * Domain-Oriented Programming * Generative Programming * Ambient Intelligence * Unanticipated Software Evolution * Design Patterns * Educational Perspectives Breakout Groups *************** We want to promote to take advantage of meeting other Lispers and Schemers face to face by organizing breakout groups around focused topics. Example topics: Discuss the feature set of the next version of Slime; work on details of the CLRFI process; exchange experiences with various macro systems for Scheme; detail a wishlist for R6RS; compare and enhance curricula for computer science education. And so on. In order to have effective discussions at those breakout groups, we are negotiating meeting rooms for an extra day in addition to the actual workshop with the ECOOP organizers. Submission Guidelines ********************* Potential attendants are expected to submit * either a long paper (10 pages) presenting scientific and/or empirical results about Lisp- and Scheme-based uses or new approaches for software engineering purposes * or a short essay (5 pages) defending a position about where research and practice based on Lisp and Scheme should be heading in the near future * a proposal for a breakout group (1-2 pages) describing the theme, an agenda and/or expected results Submissions should be mailed as PDF to Pascal Costanza (pc(a)p-cos.net) before the submission deadline. Please indicate whether you need an earlier notification of acceptance than the official date.

1 0

[eurolisp] Announcement International Lisp Conference 2005
by Ernst van Waning 29 Mar '05

29 Mar '05

[Please accept our apologies if you receive this message more than once] CALL FOR CONTRIBUTIONS International Lisp Conference 2005 http://www.international-lisp-conference.org Stanford University June 19-22, 2005 Sponsored by: The Association of Lisp Users Symbolic Systems Program, Stanford University General Information: The Association of Lisp Users is pleased to announce that Stanford University will host the next International Lisp Conference between June 19 and 22. ILC 2005 marks the 25th anniversary of the seminal 1980 Lisp conference held at Stanford in August of 1980. This year, the Organizing Committee of ILC 2005 is encouraging submissions in the particular areas of: functional language design and implementation, mathematical and scientific computing, artificial intelligence, data mining, business intelligence, bioinformatics, telecommunications and networking, the semantic web, music, and entertainment technologies. Further details are available at the conference web site. General correspondence on ILC 2005 may be sent to ilc2005(a)alu.org. Technical Program: Original submissions in all areas related to the conference themes are invited for the following categories: papers, exhibits, workshops, tutorials, and panel discussions. The official language of the conference is English. Important Dates: Note well: The submission deadline has been relaxed. Deadline for abstract submissions: April 5, 2005 Author notification: April 25, 2005 Deadline for final paper submission: May 25, 2005 Organizing Committee: Chair: Carl Shapiro (SRI International) Members: Rusty Johnson (ALU) Peter Lindahl (ALU) Contact: ilc05-organizing-committee(a)alu.org Program Committee: Chair: JonL White (ALU) Members: Jans Aasman (Franz, Inc.) John Adams (Space Telescope Science Institute) John Amuedo (Signal Inference Corporation) Kazuyuki Hashimoto (Electronic Arts) Larry Hunter (UCHSC) Nick Levine (Ravenbrook Limited) Christian Queinnec (Universite Paris 6) Nancy Reed (University of Hawaii) Jeff Shrager (Stanford University) Mark Stickel (SRI International) Taiichi Yuasa (Kyoto University) David Wilkins (SRI International) Contact: ilc05-program-committee(a)alu.org

1 0

[eurolisp] [ANN] 2nd European Lisp & Scheme Workshop
by Pascal Costanza 25 Mar '05

25 Mar '05

This is actually a draft announcement. We are still waiting for some information from the ECOOP organizers, and the workshop website isn't online yet (this is mainly my fault). In order not to delay the most important details any further, here is what we already have. A more detailed announcement is to follow soon. +----------------------------------------------------------------------+ | 2nd European Lisp and Scheme Workshop | | July 26 - Glasgow, Scotland - co-located with ECOOP 2005 | +----------------------------------------------------------------------+ ************************************************************************ Important - The workshop will include a keynote by Richard P. Gabriel. (pending) - We are looking for papers & for breakout group proposals! (see below) ************************************************************************ Important Dates: Submission deadline: May 16, 2005 Notification of acceptance: May 27, 2005 ECOOP early registration deadline: pending For more information contact pc(a)p-cos.net Organizers ********** Pascal Costanza, Programming Technology Lab, Vrije Universiteit Brussel Theo D'Hondt, Programming Technology Lab, Vrije Universiteit Brussel Arthur Lemmens, Independent Consultant, Amsterdam Manuel Serrano, INRIA Sophia-Antipolis, France Website: Hans Huebner, Berlin Overview ******** Lisp has a tradition of providing a fruitful basis for language design experiments for many decades. The structure of Lisp, including its current major dialects Common Lisp and Scheme, makes it easy to extend the language or even to implement entirely new dialects without starting from scratch. The Common Lisp Object System (CLOS) was the first object-oriented programming language to receive an ANSI standard. It is, arguably, the most complete and advanced object system of any language. Despite having somewhat disappeared from the radar of popular computer science, Lisp has just started to gain momentum again. There is a steadily growing interest in Lisp as such, with numerous user groups having formed recently worldwide, and Lisp's metaprogramming notions that are being transferred to other languages to different extents, as for example in AOP, MDA, DSL, and so on. This one-day workshop will address the near-future role of Lisp-based languages in research, industry and education. We want to solicit papers and suggestions for breakout groups that discuss the opportunities Lisp provides to capture and enhance the possibilities in software engineering. We also want to promote lively discussion between researchers proposing new approaches and practitioners reporting on their experience with the strengths and limitations of current Lisp technologies. Papers ****** Suggested Topics: * Macro programming * Metaprogramming * Reflection * New language features / abstractions * Case studies * Experience reports * Industrial applications * Object-Oriented Programming * Declarative Programming * Aspect-Oriented Programming * Domain-Oriented Programming * Generative Programming * Ambient Intelligence * Unanticipated Software Evolution * Design Patterns * Educational Perspectives Breakout Groups *************** We want to promote to take advantage of meeting other Lispers and Schemers face to face by organizing breakout groups around focused topics. Example topics: Discuss the feature set of the next version of Slime; work on details of the CLRFI process; exchange experiences with various macro systems for Scheme; detail a wishlist for R6RS; compare and enhance curricula for computer science education. And so on. In order to have effective discussions at those breakout groups, we are negotiating meeting rooms for an extra day in addition to the actual workshop with the ECOOP organizers. Submission Guidelines ********************* Potential attendants are expected to submit * either a long paper (10 pages) presenting scientific and/or empirical results about Lisp- and Scheme-based uses or new approaches for software engineering purposes * or a short essay (5 pages) defending a position about where research and practice based on Lisp and Scheme should be heading in the near future * a proposal for a breakout group (1-2 pages) describing the theme, an agenda and/or expected results Submissions should be mailed as PDF to Pascal Costanza (pc(a)p-cos.net) before the submission deadline. Please indicate whether you need an earlier notification of acceptance than the official date.

1 0

Re: [eurolisp] Bigger room for European Common Lisp Meeting
by Hoehle, Joerg-Cyril 20 Mar '05

20 Mar '05

Arthur and Edi, thank you very much for your endured/ing efforts. This time I'm in and no more p.o.'ed -- and will look for room & transports after registration, instead of usually doing it the other way round :). Who will be traveling from the Frankfurt area, and at what time/day? Regards, Jörg Höhle.

3 2