- pro - mailman3.common-lisp.net

[CfP] ELS'25, 18th European Lisp Symposium, May 19-20, Zurich
by Didier Verna 10 Dec '24

10 Dec '24

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 18th European Lisp Symposium Call for Papers May 19-20 2025 SGH, Zurich, Switzerland https://www.european-lisp-symposium.org/2025 Sponsered by SGH ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Special Focus ~~~~~~~~~~~~~ This year, we suggest a special focus on artifical intelligence, and meta-programming beyond macros. Invited Speakers ~~~~~~~~~~~~~~~~ Anurag Mendhekar Joerg Gutknecht Important Dates ~~~~~~~~~~~~~~~ - Registration opens: Dec 10 2024 - Submission deadline: Mar 02 2025 - Author notification: Mar 30 2025 - Final papers due: Apr 13 2025 - Early Registration: May 04 2025 - Symposium: May 19-20 2025 Scope ~~~~~ The European Lisp Symposium is a premier 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, Clojure, Racket, ACL2, AutoLisp, ISLISP, Dylan, SKILL, Hy, Shen, Carp, Janet, uLisp, Picolisp, Gamelisp, TXR, and so on. We encourage everyone interested in Lisp to participate. The European Lisp Symposium invites high quality papers about novel research results, insights and lessons learned from practical applications, and educational perspectives. We also encourage submissions about known ideas as long as they are presented in a new setting and/or in a highly elegant way. Topics include but are not limited to: - context-, aspect-, domain-oriented and generative programming - macro-, reflective-, meta- and/or rule-based development approaches - language design and implementation - language integration, inter-operation, and deployment - development methodologies, support, and environments - educational approaches and perspectives - experience reports and case studies Technical Program ~~~~~~~~~~~~~~~~~ We invite submissions in the following forms. Papers and experience reports must not overlap significantly with the authors’ previously published work in a peer reviewed publication, and must not be under review on another journal or conference. Also, authors must agree with our publication ethics and malpractice statement (cf. https://european-lisp-symposium.org/pepms.html) * Papers: technical papers of up to 8 pages that describe original results or explain known ideas in new and elegant ways. * Experience reports: papers of up to 6 pages describing a successful use of a Lisp dialect and/or analyzing obstacles that have kept it from working in practice. * Tutorials: abstracts of up to 4 pages for in-depth presentations about topics of special interest. * Demonstrations: abstracts of up to 4 pages for demonstrations of tools, libraries, and applications. For information on the submission format, please refer to the "Submission" section at https://www.european-lisp-symposium.org/2025. Submissions should be uploaded to Easy Chair at the following link: http://www.easychair.org/conferences/?conf=els2025. Note: to help us with the review process please indicate the type of submission in the title field in the submission form. Programme Chair ~~~~~~~~~~~~~~~ François-René Rideau Đặng-Vũ Bân, MuKn, USA Organizing Chair ~~~~~~~~~~~~~~~~ Didier Verna, EPITA / LRE, France Programme Committee ~~~~~~~~~~~~~~~~~~~ Conrad Barski, USA Marc Battyani, Enfabrica, USA Dave Cooper, Genworks, USA Ryan Culpepper, University of Massachusetts Boston, USA Eitaro Fukamachi, Japan Robert Goldman, SIFT, USA Gavin Gray, Brown University, USA Jason Hemann, Seton Hall University, USA Kristopher Micinski, Syracuse University, USA Marco Morazan, Seton Hall University, USA Michael Raskin, LaBRI, France Masatoshi Sano, Nayuta, Japan Dimitris Vyzovitis, Mighty Gerbils Local Chair ~~~~~~~~~~~ Yukari Hafner, Shirakumo.org, Switzerland Virtualization Team ~~~~~~~~~~~~~~~~~~~ Georgiy Tugai, Configura, Sweden Yukari Hafner, Shirakumo.org, Switzerland -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info

1 0

Unicode character naming
by Marco Antoniotti 15 Oct '24

15 Oct '24

Hello parenthetical crowd Is there a consensus about how to "name" Unicode characters, or every implementation does whatever it likes (thus breaking otherwise perfectly portable code)? Cf., #\INFINITY All the best MA PS Do not even think to use the "hey, it is an implementation-dependent thing" argument! -- Marco Antoniotti, Professor tel. +39 - 02 64 48 79 01 DISCo, University of Milan-Bicocca U14 2043 http://dcb.disco.unimib.it Viale Sarca 336 I-20126 Milan (MI) ITALY

4 7

CDR for Package-Local Nicknames [Feedback Request]
by Alexander Fedorov 13 Jul '24

13 Jul '24

Dear all, Over 10 years ago, SBCL implemented the Package-Local Nicknames (PLNs) extension. Since then, PLNs have also been adopted by multiple implementations (ABCL, CCL, ECL, Clasp, Allegro CL and LispWorks) and are now widely used in many projects. However, PLNs are still considered experimental, as stated in the SBCL manual, since there is no formal specification for them, and each implementation interprets various corner cases differently. While the need for a specification has been previously discussed, I was unable to find any publicly accessible draft for one. Therefore, I have drafted a specification intended to become a CDR document. I initially wrote this draft about a year ago and have recently revised it. You can find the latest version here: https://gleefre.github.io/cdr-package-local-nicknames/index.html. There are currently nine unresolved standardization issues, each with at least one proposed resolution. Input on those issues would be particularly helpful, but any feedback is welcome! P.S. I am sharing this link across multiple platforms to reach as many lispers as possible. This includes various mailing lists (Lisp Pro, CDR-discuss and -devel for various CL implementations); IRC channels (#commonlisp and implementation-specific ones); the Lisp Discord server; several Telegram groups; and a post on Reddit. If you have any suggestions for additional places to share the link, please let me know. My apologies to those receiving this message multiple times. Best regards, Alexander Fedorov.

8 12

Seeking early adopters for a CL product
by John Morrison 28 Jun '24

28 Jun '24

Hi All; Can't think of a better place to find people to help us refine a fledgling CL product than this list. We are seeking early adopters for our distributed situational awareness platform, key bits of which are written in Common Lisp. It's a "local first" (completely self-hosted) slippy-map, plus: a 3D globe, a data fabric, an OpenStreetmap PostGIS database, a nominatim geocoder, etc. Here <https://drive.google.com/file/d/1bI7RyHD0pgkXdCDxk6Z4RoRwUB9QiFyv/view?usp=…> is the two-pager. Please send any replies not to the list, but to me directly. Thanks in advance, John Morrison (who actually used a wire-wrapped CADR back in the day, and owns a MacIvory whose Mac II host motherboard probably needs to be recapped) --- John Morrison <jm(a)symbolic-simulation.com> Chief Technology Officer Symbolic Simulation, LLC <https://www.symbolic-simulation.com> m: (617) 388-3071 <+1-617-388-3071> <https://www.symbolic-simulation.com> *CONFIDENTIALITY NOTICE: The information transmitted by this email is intended only for the person or entity to which it is addressed. This email may contain proprietary, business-confidential, and/or privileged material. If you are not the intended recipient of this message, be aware that any use, review, retransmission, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this in error, please contact the sender and delete the material from all computers.* --- John Morrison <jm(a)symbolic-simulation.com> Chief Technology Officer Symbolic Simulation, LLC <https://www.symbolic-simulation.com> m: (617) 388-3071 <+1-617-388-3071> <https://www.symbolic-simulation.com> *CONFIDENTIALITY NOTICE: The information transmitted by this email is intended only for the person or entity to which it is addressed. This email may contain proprietary, business-confidential, and/or privileged material. If you are not the intended recipient of this message, be aware that any use, review, retransmission, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this in error, please contact the sender and delete the material from all computers.*

1 0

CLAST reworked
by Marco Antoniotti 26 Jun '24

26 Jun '24

Hi just in case you may be interested, I updated the CLAST documentation (and posted a blog post on https://within-parens.blogspot.com/2024/06/clast-reworked.html) All the best Marco -- Marco Antoniotti, Professor tel. +39 - 02 64 48 79 01 DISCo, University of Milan-Bicocca U14 2043 http://dcb.disco.unimib.it Viale Sarca 336 I-20126 Milan (MI) ITALY

1 0

a short venting about scheme
by Attila Lendvai 25 Jun '24

25 Jun '24

context: i'm diving deeper into scheme for the first time in my life... and i have to say that i used to have this impression throughout the years i was hacking CL that scheme is a more cleaned up lisp, that it's more thought out than CL. but i don't think that anymore. it's simply leaner, but it's worse at some key parts (and it's not even due to hard compromises, it's simply not designed well at some parts). one example, that initiated this venting, is the API of WITH-EXCEPTION-HANDLER. i don't want to get too deep into this, i just want to express a glimpse of contrary opinion that i have never met thoughout my years of lisp hacking: scheme is not a cleaned up CL. it's just another dialect. -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- “Keep this thought handy when you feel a bit of rage coming on: it isn't manly to be enraged. Rather, gentleness and civility are more human, and therefore manlier. A real person doesn't give way to anger and discontent, and such a person has strength, courage, and endurance ― unlike the angry and complaining. The nearer a man comes to a calm mind, the closer he is to strength.” — Marcus Aurelius (121–180), 'Meditations'

7 9

CLAST: major refactoring
by Marco Antoniotti 23 Jun '24

23 Jun '24

Hi I just pushed a major rework of the CLAST internals. The system is now pretty much usable, of course with an emphasis on the "pretty much". I will welcome any bug report to improve it. Tested on LW, SBCL and Allegro 11.x. CMUCL and CCL will work as well (just need a little time). Probably also ECL. The naughty Java crowd giving us ABCL instead needs to do some work (naughty, naughty, naughty)! People working on other implementations, please drop me a line. https://clast.sf.net (The documentation is not up to date, but that's minor) Enjoy -- Marco Antoniotti, Professor tel. +39 - 02 64 48 79 01 DISCo, University of Milan-Bicocca U14 2043 http://dcb.disco.unimib.it Viale Sarca 336 I-20126 Milan (MI) ITALY

1 0

static-vectors:free-static-vector for LispWorks
by shubhamayare＠yahoo.co.in 31 May '24

31 May '24

Hello all, Currently, static-vectors:free-static-vector on LispWorks is an empty function.This function should free an array allocated with static-vectors:make-static-vector.On LispWorks, static-vectors:make-static-vector uses make-array with :allocation :static.Then, what should be an appropriate definition for free-static-vector? I discovered raw::free-an-object that does what is intended. Does anyone know if there'sa better candidate for the job? Thanks and Best,Shubhamkar Ayare / digikar

2 2

Fwd: Git hunk header regex for CL
by Scott L. Burson 01 Apr '24

01 Apr '24

Hi all, I am using Git to manage a CL project I am working on, and have noticed that there is no predefined regular expression to pull out "hunk headers". If you look at 'git diff' output, each hunk (sequence of consecutive lines with differences noted) has a header line, which is intended to show the first line of the top-level syntactic object (function definition, class declaration, etc.) that contains the hunk, so you can quickly see what function, class, etc. it is within. To find the appropriate header line for each hunk, Git scans backwards from the top of the hunk with a regular expression, and takes the first line that matches. The regex to use, of course, depends on the language of the source file. Git has a table of built-in regexes for a number of languages, including Scheme, but there is neither a generic Lisp entry nor a more specific CL entry. I am inclined to submit one for inclusion, but I wanted to bounce it off you folks first. Here is the current Scheme regex. This is in POSIX Extended ("ERE") syntax: ^[\t ]*(\\(((define|def(struct|syntax|class|method|rules|record|proto|alias)?)[-*/ \t]|(library|module|struct|class)[*+ \t]).*)$ This is unfortunately not general enough to work for CL, as it doesn't pick up 'defun', though it does allow some other CL constructs. So I started to think about what would be good for CL. Some possibilities: 1. Simply match any line that starts with an open paren in column 0. The upside of this simple rule is that it allows for arbitrary top-level construct names. But if you indent your defuns for some reason, it will overlook them. 2. Match any line that starts with '(def', even if indented. This could have false positives. 3. Match either (1) or (2). I'm leaning toward (3), but would like to hear your thoughts. Certainly, we could use a more specific regex that matches only predefined CL top-level constructs, but this seems wrong to me considering that CL encourages us to define macros to add such constructs when we see a need. -- Scott

3 2

DEFTYPE and SATISFIES
by Marco Antoniotti 22 Feb '24

22 Feb '24

Hi I just stumbled upon this and I need confirmation. You cannot do anything like this, can you? *(defstruct foo x)* *(deftype foo-with-x (x) (satisfies 'foo-with-x-p)) ; No `x'!* *(typep (make-foo :x 42) '(foo-with-x 42))* I.e., there is no way to pass the *x* to *foo-with-x-p*, is there? All the best MA -- Marco Antoniotti, Professor tel. +39 - 02 64 48 79 01 DISCo, Università Milano Bicocca U14 2043 http://dcb.disco.unimib.it Viale Sarca 336 I-20126 Milan (MI) ITALY

4 6