***********************************************************************
* *
* International Lisp Conference 2010 *
* October 19-21, 2010 *
* John Ascuaga's Nugget (Casino) *
* Reno/Sparks, Nevada, USA (near Lake Tahoe) *
* *
* Collocated with SPLASH 2010 (OOPSLA & DLS & more) *
* see also http://splashcon.org as well as *
* http://www.dynamic-languages-symposium.org/dls-10/ *
* *
* In association with ACM SIGPLAN (PENDING) *
* *
***********************************************************************
The Association of Lisp Users is pleased to announce that the 2010
International Lisp Conference will be held in Reno, Nevada, in
collocation with SPLASH 2010. The scope includes all areas related to
the Lisp family of programming languages.
Accepted papers will be published in the ACM Digital Library (PENDING).
Extended Abstracts and Papers must be written in English and submitted
electronically at http://www.easychair.org/conferences?conf=ilc2010 in
PDF or WORD format. If an Extended Abstract is submitted, it must be
between 2 and 4 pages, with full paper to follow before final deadline.
Final submissions must not exceed 15 pages and need to use the ACM
format, for which templates which can be found at:
http://www.acm.org/sigs/pubs/proceed/template.html.
Important Dates:
****************
* Deadline for Abstract Submission August 1, 2010
* Deadline for Paper Submission September 6, 2010
* Author notification September 20, 2010
* Final paper due (in electronic form) October 5, 2010
* Conference October 19-21, 2010
Scope:
******
Lisp is one of the greatest ideas from computer science and a major
influence for almost all programming languages and for all
sufficiently complex software applications.
The International Lisp Conference is a forum for the discussion of
Lisp and, in particular, the design, implementation and application of
any of the Lisp dialects. We encourage everyone interested in Lisp to
participate.
We invite high quality submissions in all areas involving Lisp
dialects and any other languages in the Lisp family, including, but
not limited to, ACL2, AutoLisp, Clojure, Common Lisp, ECMAScript,
Dylan, Emacs Lisp, ISLISP, Racket, Scheme, etc.
Topics may include any and all combinations of Lisp and:
* Language design and implementation
* Language critique
* Language integration, inter-operation and deployment
* Applications (especially commercial)
* 'Pearls' (of wisdom)
* Experience reports and case studies
* Reflection, meta-object protocols, meta-programming
* Domain-specific languages
* Programming paradigms and environments
* Parallel and distributed computing
* Software evolution
* Theorem proving
* Scientific computing
* Data mining
* Semantic web
We also encourage submissions about known ideas as long as they are
presented in a new setting and/or in a highly elegant way.
Authors concerned about the appropriateness of a topic may communicate
by electronic mail with the program chair prior to submission.
Each paper should explain its contributions in both general and
technical terms, identifying what has been accomplished, explaining
why it is significant, and comparing it with previous work. Authors
should strive to make their papers understandable to a broad audience.
Each paper will be judged according to its significance, novelty,
correctness, clarity, and elegance.
The official language of the conference is English. Some further
information is available at the conference web site, with more details
added later. See: http://www.international-lisp-conference.org
Technical Program:
******************
Original submissions in all areas related to the conference themes are
invited for the following categories.
* Papers: Technical papers of up to 15 pages that describe original
results or explain known ideas in new and elegant ways, or extended
abstracts of 4 pages soon followed by the corresponding full paper.
* Demonstrations: Abstracts of up to 4 pages for demonstrations of
tools, libraries, and applications.
* Tutorials: Abstracts of up to 4 pages for in-depth presentations
about topics of special interest for at least 90 minutes and up to
180 minutes.
* Workshops: Abstracts of up to 4 pages for groups of people who
intend to work on a focused topic for half a day.
* Panel discussions: Abstracts of up to 4 pages for discussions about
current themes. Panel discussion proposals must mention panel
members who are willing to partake in a discussion.
* Lightning talks: Abstracts of up to one page for talks to last for
no more than 5 minutes.
Depending on the technical content, each submitted paper will be
classified by the program committee as either a technical paper or as
an experience paper; and authors will be informed about this
classification. Note that all interesting submissions are considered
valuable contributions to the success of the ILC series of
conferences. As in past ILC's since 2007, accepted papers in both
categories will be presented at the conference, included in the
proceedings, and submitted to the ACM digital library.
Organizing Committee:
*********************
* General Chair:
JonL White The Ginger IceCream Factory of Palo Alto, ALU
* Program Chair:
Antonio Leitao Instituto Superior Tecnico/INESC-ID
* Conference Treasurer:
Duane Rettig Franz, Inc., ALU Director
* Publicity Chair:
Daniel Herring ALU Director
* ALU Treasurer:
Rusty Johnson TASC, Inc., ALU Director
Program Committee:
******************
* Antonio Leitao Instituto Superior Tecnico/INESC-ID, Portugal
* Alex Fukunaga University of Tokyo, Japan
* Charlotte Herzeel Vrije Universiteit Brussel, Belgium
* Christophe Rhodes Goldsmiths College, University of London, UK
* Didier Verna EPITA Research and Development Laboratory, France
* Duane Rettig Franz, Inc., USA
* Giuseppe Attardi University of Pisa, Italy
* Jeff Shrager Symbolic Systems Program, Stanford University, USA
* Joe Marshall Google, Inc., USA
* Julian Padget University of Bath, UK
* Keith Corbet Clozure Associates, USA
* Kent Pitman PTC, USA
* Manuel Serrano INRIA Sophia Antipolis, France
* Marc Feeley University of Montreal, Canada
* Marie Beurton-Aimar University of Bordeaux 1, France
* Mark Stickel SRI International, USA
* Matthias Felleisen Northeastern University, USA
* Scott McKay ITA Software, USA
Contacts:
*********
* Questions: ilc10-organizing-committee at alu.org
* Program Chair: ilc2010 at easychair.org
For more information, see http://www.international-lisp-conference.org
|
Didier Verna's scientific blog: Lisp, Emacs, LaTeX and random stuff. |
|
Monday, June 7 2010
ILC 2010 announced
By Didier Verna on Monday, June 7 2010, 11:34 - Lisp
Monday, May 10 2010
ELS 2010 paper now available
By Didier Verna on Monday, May 10 2010, 13:54 - Lisp
My paper entitled "CLoX: Common Lisp Objects for XEmacs", presented at the 3rd European Lisp Symposium last week, is now available for download on my website.
You can find it here.
You can find it here.
Sunday, May 2 2010
How to (not) make a good presentation
By Didier Verna on Sunday, May 2 2010, 13:11 - Miscellaneous
Based on a recent experience, here is some piece of advice on how to (not) make a good "invited speaker" scientific presentation.
1. Don't think you have been invited because you won a Nygaard price or whatever, but because you have designed a cool language.
2. If you really need to start your talk by showing off your latest book to the audience, at least consider offering one to the lab that has just invited you.
3. Don't spend half of your presentation on your CV (My Life, My Accomplishments etc.), because that's not why you were invited, and because the audience doesn't give a damn.
4. When you have 60 minutes, don't come with the usual 300 slides that you carry everywhere and pick some at random. Your presentation won't make any sense.
5. Before coming, try to take at least 5 minutes to figure out who you're going to talk to, what they know, what they don't. This will help you make more sense out of your presentation, and then, perhaps the audience will actually learn something.
6. Try to understand that when you have an idea, it's not necessarily a good one, and when others have ideas, they're not necessarily bad ones.
7. Try not to be dogmatic because this doesn't look so good to scientists. Show some humility. It is better to have many questions than to have all the answers.
8. If you really want to make people believe that you have actually done some bibliography in your research, try to cite at least one paper more recent than the first OOPSLA in 1986. Otherwise, the picture of your knowledge about other current programming languages is, like, pretty explicit, and a bit sad.
9. Understand that trying to sell your product will never work with researchers.
Well, I guess in summary, try to show some interest for the rest of the world, and especially for your audience, or just don't come. Otherwise, you will look like a fool.
1. Don't think you have been invited because you won a Nygaard price or whatever, but because you have designed a cool language.
2. If you really need to start your talk by showing off your latest book to the audience, at least consider offering one to the lab that has just invited you.
3. Don't spend half of your presentation on your CV (My Life, My Accomplishments etc.), because that's not why you were invited, and because the audience doesn't give a damn.
4. When you have 60 minutes, don't come with the usual 300 slides that you carry everywhere and pick some at random. Your presentation won't make any sense.
5. Before coming, try to take at least 5 minutes to figure out who you're going to talk to, what they know, what they don't. This will help you make more sense out of your presentation, and then, perhaps the audience will actually learn something.
6. Try to understand that when you have an idea, it's not necessarily a good one, and when others have ideas, they're not necessarily bad ones.
7. Try not to be dogmatic because this doesn't look so good to scientists. Show some humility. It is better to have many questions than to have all the answers.
8. If you really want to make people believe that you have actually done some bibliography in your research, try to cite at least one paper more recent than the first OOPSLA in 1986. Otherwise, the picture of your knowledge about other current programming languages is, like, pretty explicit, and a bit sad.
9. Understand that trying to sell your product will never work with researchers.
Well, I guess in summary, try to show some interest for the rest of the world, and especially for your audience, or just don't come. Otherwise, you will look like a fool.
Wednesday, April 14 2010
New article in JUCS journal
By Didier Verna on Wednesday, April 14 2010, 17:06 - Lisp
My article entitled "Revisiting the Visitor: the Just Do It Pattern" has just been published in the JUCS journal, Volume 16, Issue 2.
You can find it here.
You can find it here.
Tuesday, March 9 2010
Paper accepted at ELS 2010
By Didier Verna on Tuesday, March 9 2010, 16:09 - Lisp
I'm happy to announce that I will be presenting a paper at ELS 2010, the next European Lisp Symposium, in Lisbon. The abstract is given below:
CloX: Common Lisp Objects for XEmacs
CloX is an ongoing attempt to provide a full Emacs Lisp implementation of the Common Lisp Object System, including its underlying meta-object protocol, for XEmacs. This paper describes the early development stages of this project. CloX currently consists in a port of Closette to Emacs Lisp, with some additional features, most notably, a deeper integration between types and classes and a comprehensive test suite. All these aspects are described in the paper, and we also provide a feature comparison with an alternative project called EIEIO.
CloX: Common Lisp Objects for XEmacs
CloX is an ongoing attempt to provide a full Emacs Lisp implementation of the Common Lisp Object System, including its underlying meta-object protocol, for XEmacs. This paper describes the early development stages of this project. CloX currently consists in a port of Closette to Emacs Lisp, with some additional features, most notably, a deeper integration between types and classes and a comprehensive test suite. All these aspects are described in the paper, and we also provide a feature comparison with an alternative project called EIEIO.
Paper accepted at TUG 2010
By Didier Verna on Tuesday, March 9 2010, 08:36 - LaTeX
Hello,
I'm happy to announce that I will be presenting a paper at TUG 2010, in San Francisco, for the 2^5th birthday of TeX. The abstract is given below:
Classes, Styles, Conflicts: the Biological Realm of LaTeX
Every LaTeX user faces the "compatibility nightmare" one day or another. With so much intercession capabilities at hand (LaTeX code being able to redefine itself at will), a time comes inevitably when the compilation of a document fails, due to a class/style conflict. In an ideal world, class/style conflicts should only be a concern for package maintainers, not end-users of LaTeX. Unfortunately, the world is real, not ideal, and end-user document compilation does break.
As both a class/style maintainer and a document author, I tried several times to come up with some general principles or a systematic approach to handling class/style cross-compatibility in a smooth and gentle manner, but I ultimately failed. Instead, one Monday morning, I woke up with this vision of the LaTeX biotope, an emergent phenomenon whose global behavior cannot be comprehended, because it is in fact the result of a myriad of "macro"-interactions between small entities, themselves in perpetual evolution.
In this presentation, I would like to draw bridges between LaTeX and biology, by viewing documents, classes and styles as living beings constantly mutating their geneTeX code in order to survive \renewcommand attacks...
I'm happy to announce that I will be presenting a paper at TUG 2010, in San Francisco, for the 2^5th birthday of TeX. The abstract is given below:
Classes, Styles, Conflicts: the Biological Realm of LaTeX
Every LaTeX user faces the "compatibility nightmare" one day or another. With so much intercession capabilities at hand (LaTeX code being able to redefine itself at will), a time comes inevitably when the compilation of a document fails, due to a class/style conflict. In an ideal world, class/style conflicts should only be a concern for package maintainers, not end-users of LaTeX. Unfortunately, the world is real, not ideal, and end-user document compilation does break.
As both a class/style maintainer and a document author, I tried several times to come up with some general principles or a systematic approach to handling class/style cross-compatibility in a smooth and gentle manner, but I ultimately failed. Instead, one Monday morning, I woke up with this vision of the LaTeX biotope, an emergent phenomenon whose global behavior cannot be comprehended, because it is in fact the result of a myriad of "macro"-interactions between small entities, themselves in perpetual evolution.
In this presentation, I would like to draw bridges between LaTeX and biology, by viewing documents, classes and styles as living beings constantly mutating their geneTeX code in order to survive \renewcommand attacks...
Thursday, February 25 2010
Translucent XEmacs coming in hot !!
By xemacs on Thursday, February 25 2010, 13:25 - (X)Emacs
I'm uploading a set of changes to the XEmacs 21.5 Mercurial repository right now. These changes implement a new face property named "background-placement" which makes an XEmacs frame "slide" over a face's background pixmap when the property is set to 'absolute.
If you do this on the default face, then you can achieve some sort of pseudo-translucency, for example by using the same (or a darkened version of) the root window's background pixmap.
Here are a couple of screenshots that illustrate this.
If you do this on the default face, then you can achieve some sort of pseudo-translucency, for example by using the same (or a darkened version of) the root window's background pixmap.
Here are a couple of screenshots that illustrate this.
Monday, February 15 2010
RT for Emacs Lisp, version 1.0
By Didier Verna on Monday, February 15 2010, 17:03 - Lisp
I'm happy to announce the first public version of RT for Emacs Lisp, a port of the original Common Lisp regression testing package.
Grab it here.
Grab it here.
ELW 2010: 7th European Lisp Workshop
By Didier Verna on Monday, February 15 2010, 09:04 - Lisp
+------------------------------------------------------------+
| CALL FOR PAPERS |
| 7th European Lisp Workshop |
| June 21/22, Maribor, Slovenia - co-located with ECOOP 2010 |
+------------------------------------------------------------+
Important Dates
===============
Submission deadline: April 19, 2010
Notification of acceptance: May 05, 2010
ECOOP early registration deadline: May 10, 2010
7th European Lisp Workshop: June 21 or 22, 2010 (tbdl)
Please note that registration must be done with ECOOP itself.
For more information visit http://www.european-lisp-workshop.org
Contact: Didier Verna, didier@lrde.epita.fr
Invited Speaker
===============
Manuel Serrano (INRIA, France)
http://www-sop.inria.fr/members/Manuel.Serrano/
Overview
========
"...Please don't assume Lisp is only useful for Animation and
Graphics, AI, Bio-informatics, B2B and E-Commerce, Data Mining,
EDA/Semiconductor applications, Expert Systems, Finance, Intelligent
Agents, Knowledge Management, Mechanical CAD, Modeling and Simulation,
Natural Language, Optimization, Research, Risk Analysis, Scheduling,
Telecom, and Web Authoring just because these are the only things they
happened to list."
-- Kent Pitman
Lisp, one of the eldest computer languages still in use today, is
gaining momentum again. The structure of Lisp makes it easy to extend
the language or even to implement entirely new dialects without
starting from scratch, making it the ideal candidate for writing
Domain Specific Languages. Common Lisp, with the Common Lisp Object
System (CLOS), was the first object-oriented programming language to
receive an ANSI standard and remains the most complete and advanced
object system of any programming language, while influencing many
other object-oriented programming languages that followed.
This workshop will address the near-future role of Lisp-based
languages in research, industry and education. We solicit
contributions that discuss the opportunities Lisp provides to capture
and enhance the possibilities in software engineering. We 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.
The workshop will have two components: there will be formal talks, and
interactive turorial/demo/coding sessions.
Papers
======
Formal presentations in the workshop should take between 20 minutes
and half an hour; additional time will be given for questions and
answers. Suggested topics include (but are not limited to):
- Context-, aspect-, domain-oriented and generative programming
- Macro-, reflective-, meta- and/or rule-based development approaches
- Protocol meta-programming and libraries
- New language features and abstractions
- Software evolution
- Development aids
- Persistent systems
- Dynamic optimization
- Implementation techniques
- Hardware Support
- Efficiency, distribution and parallel programming
- Educational approaches and perspectives
- Experience reports and case studies
Interactive Tutorial/Demo/Coding Sessions
=========================================
Additionally, we invite less formal talks in the form of interactive
tutorial/demo/coding sessions. The purpose of these sessions is both
to demonstrate and receive feedback on any interesting Lisp system,
either stable or under development. Being less formal than technical
paper presentations, these sessions are expected to be highly
interactive.
Submission Guidelines
=====================
Potential contributors are encouraged to submit:
- a long paper (around 10 pages) presenting scientific and/or
empirical results about Lisp-based uses or new approaches for
software engineering purposes,
- a short essay (5 pages) defending a position about where
research, practice or education based on Lisp should be heading in
the near future,
- a proposal for an interactive tutorial/demo/coding session (1-2
pages) describing the involved library or application, and the
subject of the session.
Papers (both long and short) should be formatted following the ACM SIGS
guidelines and include ACM classification categories and terms (see below).
Authors will later be required to sign an ACM copyright form, as the workshop
proceedings will be published in the ACM Digital Library.
For more information on the submission guidelines and the ACM keywords, see:
http://www.acm.org/sigs/publications/pr ... -templates
http://www.acm.org/about/class/1998
Submissions should be uploaded to Easy Chair, at the following address:
http://www.easychair.org/conferences/?conf=elw2010
Organizers
==========
Didier Verna, EPITA Research and Development Laboratory, Paris
Charlotte Herzeel, Programming Technology Lab, Vrije Universiteit, Brussel
Robert Strandh, LaBRI, University of Bordeaux 1, France
Christophe Rhodes, Goldsmiths College, University of London
Monday, January 11 2010
Master 2 Internship
By Didier Verna on Monday, January 11 2010, 11:25 - Lisp
Just a quick note to let you know that I've just opened a page with internship propositions for Master 2 students. The page in question can be found here.
Friday, October 23 2009
Spotlight
By Didier Verna on Friday, October 23 2009, 13:50 - Miscellaneous
On Mac OS X, there are lots of very good reasons why syslogd could start eating 100% of your CPU. Plenty of discussions about this on the net out there.
Well, here's one more (very good) reason:
If all of a sudden, your Time Machine backup process appears to be slower than usual, and if the backup disk is not unmounted after a backup has finished, it could be that Spotlight is trying to index it. Stupid. Mine currently has an ETA of 55 hours :-)
Well, here's one more (very good) reason:
If all of a sudden, your Time Machine backup process appears to be slower than usual, and if the backup disk is not unmounted after a backup has finished, it could be that Spotlight is trying to index it. Stupid. Mine currently has an ETA of 55 hours :-)
Monday, September 21 2009
FiXme 4.0 is out !
By Didier Verna on Monday, September 21 2009, 16:27 - LaTeX
I'm happy to announce FiXme version 4.0
#### WARNING: this is a major release containing many new features and heavy
#### internals refactoring. FiXme 4.0 comes with unprecedented flexibiity,
#### unrivalled extensibility and unchallenged backward-INcompatibility.
What's new in version 4.0
=========================
* Support for collaborative annotations
suggested by Michael Kubovy
** Support for "targeted" notes and environments
(highlighting a portion of text), suggested by Mark Edgington.
** Support for "floating" notes
(not specific to any portion of text), suggested by Rasmus Villemoes.
** Support for alternate layout autoswitch in TeX's inner mode
suggested by Will Robertson.
** Support for automatic language tracking in multilingual documents
** Support for themes
** Extended support for user-provided layouts
** Support for key=value argument syntax in the whole user interface
** New command \fxsetup
** Homogenize log and console messages
** Heavy internals refactoring
Description
===========
FiXme is a collaborative annotation tool for LaTeX documents. Annotating a
document refers here to inserting meta-notes, that is, notes that do not
belong to the document itself, but rather to its development or reviewing
process. Such notes may involve things of different importance levels, ranging
from simple "fix the spelling" flags to critical "this paragraph is a lie"
mentions. Annotations like this should be visible during the development or
reviewing phase, but should normally disapear in the final version of the
document.
FiXme is designed to ease and automate the process of managing collaborative
annotations, by offering a set of predefined note levels and layouts, the
possibility to register multiple note authors, to reference annotations by
listing and indexing etc. FiXme is extensible, giving you the possibility to
create new layouts or even complete "themes", and also comes with support for
AUC-TeX.
FiXme homepage: http://www.lrde.epita.fr/~didier/softwa ... .php#fixme
#### WARNING: this is a major release containing many new features and heavy
#### internals refactoring. FiXme 4.0 comes with unprecedented flexibiity,
#### unrivalled extensibility and unchallenged backward-INcompatibility.
What's new in version 4.0
=========================
* Support for collaborative annotations
suggested by Michael Kubovy
** Support for "targeted" notes and environments
(highlighting a portion of text), suggested by Mark Edgington.
** Support for "floating" notes
(not specific to any portion of text), suggested by Rasmus Villemoes.
** Support for alternate layout autoswitch in TeX's inner mode
suggested by Will Robertson.
** Support for automatic language tracking in multilingual documents
** Support for themes
** Extended support for user-provided layouts
** Support for key=value argument syntax in the whole user interface
** New command \fxsetup
** Homogenize log and console messages
** Heavy internals refactoring
Description
===========
FiXme is a collaborative annotation tool for LaTeX documents. Annotating a
document refers here to inserting meta-notes, that is, notes that do not
belong to the document itself, but rather to its development or reviewing
process. Such notes may involve things of different importance levels, ranging
from simple "fix the spelling" flags to critical "this paragraph is a lie"
mentions. Annotations like this should be visible during the development or
reviewing phase, but should normally disapear in the final version of the
document.
FiXme is designed to ease and automate the process of managing collaborative
annotations, by offering a set of predefined note levels and layouts, the
possibility to register multiple note authors, to reference annotations by
listing and indexing etc. FiXme is extensible, giving you the possibility to
create new layouts or even complete "themes", and also comes with support for
AUC-TeX.
FiXme homepage: http://www.lrde.epita.fr/~didier/softwa ... .php#fixme
DoX v2.0 (2009/09/21) is out
By Didier Verna on Monday, September 21 2009, 08:27 - LaTeX
I'm happy to announce the release of DoX v2.0 (2009/09/21).
New in this version:
* Optional argument to \doxitem idxtype option to change the item's index type
* Optional argument to \Describe<Item> and the <Item> environment
noprint option to avoid marginal printing
noindex option to avoid item indexing
* Extend \DescribeMacro, \DescribeEnv and their corresponding environments with the same features
The doc package provides LaTeX developers with means to describe the usage and the definition of new commands and environments. However, there is no simple way to extend this functionality to other items (options or counters for instance). DoX is designed to circumvent this limitation, and provides some improvements over the existing functionality as well.
New in this version:
* Optional argument to \doxitem idxtype option to change the item's index type
* Optional argument to \Describe<Item> and the <Item> environment
noprint option to avoid marginal printing
noindex option to avoid item indexing
* Extend \DescribeMacro, \DescribeEnv and their corresponding environments with the same features
The doc package provides LaTeX developers with means to describe the usage and the definition of new commands and environments. However, there is no simple way to extend this functionality to other items (options or counters for instance). DoX is designed to circumvent this limitation, and provides some improvements over the existing functionality as well.
Monday, September 14 2009
DoX version 1.0 (2009/09/11) is now available
By Didier Verna on Monday, September 14 2009, 07:49 - LaTeX
I'm happy to annouce the first public version of the DoX package for LaTeX2e.
The doc package provides LaTeX developers with means to describe the usage and the definition of new macros and environments. However, there is no simple way to extend this functionality to other items (options or counters for instance). The dox package is designed to circumvent this limitation.
The doc package provides LaTeX developers with means to describe the usage and the definition of new macros and environments. However, there is no simple way to extend this functionality to other items (options or counters for instance). The dox package is designed to circumvent this limitation.
Wednesday, July 22 2009
FiXme 3.4 is out
By Didier Verna on Wednesday, July 22 2009, 11:42 - LaTeX
I'm happy to announce the next edition of FiXme: version 3.4
New in this release:
** \fixme, \fxerror, \fxwarning and \fxnote are now robust
** Fix incompatibility with KOMA-Script classes when the lox file is inexistent
FiXme provides you with a way of inserting fixme notes in documents. Such notes can appear in the margin of the document, as index entries, in the log file and as warnings on stdout. It is also possible to summarize them in a list, and in the index. When you switch from draft to final mode, any remaining fixme note will be logged, but removed from the document's body. Additionally, critical notes will abort compilation with an informative message. FiXme also comes with support for AUC-TeX.
New in this release:
** \fixme, \fxerror, \fxwarning and \fxnote are now robust
** Fix incompatibility with KOMA-Script classes when the lox file is inexistent
FiXme provides you with a way of inserting fixme notes in documents. Such notes can appear in the margin of the document, as index entries, in the log file and as warnings on stdout. It is also possible to summarize them in a list, and in the index. When you switch from draft to final mode, any remaining fixme note will be logged, but removed from the document's body. Additionally, critical notes will abort compilation with an informative message. FiXme also comes with support for AUC-TeX.
Wednesday, April 29 2009
And what about Erlang ??
By Didier Verna on Wednesday, April 29 2009, 15:02 - Miscellaneous
Once again, I've been puzzled by Sebesta's "Concepts of Programming languages" book. I've just read the chapter on language-level support for concurrent programming and there's not even a single line on Erlang. I can't figure out how that's possible.
Now waiting to see if Erlang is going to appear in the chapter on functional languages, but for some reason, I have a bad feeling about this...
Now waiting to see if Erlang is going to appear in the chapter on functional languages, but for some reason, I have a bad feeling about this...
Friday, April 24 2009
ACCU 2009 Material
By Didier Verna on Friday, April 24 2009, 16:04 - Lisp
Now that my talk at ACCU 2009 is over, it's okay to post the material here. So I've just uploaded the slides in PDF, and the accompanying source code. You will find all that material here. Be sure to start by opening the tarball and reading the README file. Then you can look at the source code and browse the slides in the same time.
Enjoy !
Enjoy !
Wednesday, April 15 2009
Concepts of Programming Languages
By Didier Verna on Wednesday, April 15 2009, 19:47 - Miscellaneous
These days, I'm reading "Concepts of Programming languages", 8th edition, by Robert W. Sebesta (Addison Wesley). In the category of programming languages comparison books, this is all in all a fair one, especially after having read the crappy "Comparative Programming Languages", 3rd edition, by Clark (Addison Wesley).
As in all those similar books, the room for Lisp is obviously miserable, but that is not very surprising. At least Sebesta seems to know something about it... but wait ! That was until yesterday.
Yesterday, I read chapter 12 (Support for Object Oriented Programming), and this reading pretty much ruined my fun, my evening, and the little consideration I had for the author. On page 508 you can find this:
And there's even a reference to the CLOS specification reference document.
Since the book is suddenly turning the Big Circus way, let's not stop just here. A couple of pages later, there's an interview of Bjarne Stroustrup, for whom having invented C++ is obviously not enough, and so claims that
That's it boys. These guys have no clue whatsoever.
:-(
As in all those similar books, the room for Lisp is obviously miserable, but that is not very surprising. At least Sebesta seems to know something about it... but wait ! That was until yesterday.
Yesterday, I read chapter 12 (Support for Object Oriented Programming), and this reading pretty much ruined my fun, my evening, and the little consideration I had for the author. On page 508 you can find this:
CLOS, an object-oriented version of Lisp, also supports functional programming.
And there's even a reference to the CLOS specification reference document.
Since the book is suddenly turning the Big Circus way, let's not stop just here. A couple of pages later, there's an interview of Bjarne Stroustrup, for whom having invented C++ is obviously not enough, and so claims that
Currently, C++ is the best language for multi-paradigm programming.
That's it boys. These guys have no clue whatsoever.
:-(
Wednesday, April 1 2009
:o( Smilisp :o) A new and revolutionary dialect of Lisp
By Didier Verna on Wednesday, April 1 2009, 08:41 - Lisp
Today, I just released :o( Smilisp :o), a new dialect of Lisp featuring a new paradigm called "Emotional Programming". This is truely a revolution in the Lisp world...
The logo is not exactly like that, but my blogging software wants to put smileys everwhere...
Get it here and enjoy !
:-)
The logo is not exactly like that, but my blogging software wants to put smileys everwhere...
Get it here and enjoy !
:-)
Tuesday, March 31 2009
Binary Methods Programming: the CLOS Perspective
By Didier Verna on Tuesday, March 31 2009, 07:33 - Lisp
The Journal version of this paper of mine is finally available. This is an extended version of the paper I presented at the first European Lisp Symposium last year. It's about twice as long and contains much more details.
Although it's a journal article, the PDF is freely available at the Journal's website.
Although it's a journal article, the PDF is freely available at the Journal's website.
« previous entries - page 7 of 9 - next entries »
|
|
