clisp-list — general help and discussion

[clisp-list] bug? at least explanation sought

[<don...@is...>]

This probably only happens in #+unix and I so far only can
reproduce it when running clisp from an emacs shell buffer:

  Type :h and hit Enter for context help.                                                     

  [1]> 1
  2
  3
I use emacs to create three lines: I type 1, c-o, c-f, 2, c-o, c-f, 3
then enter to send it all

  1
  [2]> 2
  [3]> 3
as expected I get three top level events.

  [4]> (with-keyboard (read-char *keyboard-input*))
  y
  #S(SYSTEM::INPUT-CHARACTER :CHAR #\y :BITS 0 :FONT 0 :KEY NIL)

now try that again
  [5]> 1
  2
  3
  1
  [6]> 

and now the top level only sees the first line.

Outside of emacs I don't even know how to send three lines at once.

I see in src/keyboard.lsp that under #+unix with-keyboard sets *keyboard-input*,
but setting it back to nil does not make the multiple lines get read again.

So what's going on here?

Re: [clisp-list] compile on i686 issue for advice/comment please

[Kaz K. <ka...@ky...>]

On 2025-08-16 05:37, C Habs wrote:
> Hello clisp-list
> 
> Trying to compile latest clisp  ( that checked out from the master branch
> on gitlab).
> The computer (laptop) is a [old] linux 32bit  celeron M 440  (slackware).
> 
> All dependencies present (i think).
> 
> The problem seems to be when using the flag, --with-threads=POSIX_THREADS
> as without it, all compiles through.
> 
> With the flag the build bails out at 'configure' time.
> 
> Question [firstly I suppose]:  does 'threads' only work on  64 bit arch,
> because there seems to be no trouble on 64 bit arch   ?
> 
> If the above is a 'yes', then no need to go further perhaps.
> 
> Question:  what is spvw.'x'  (.d .c etc)  doing and why is it an issue on
> 32 bit arch ?

spvw.d is the file from which I learned the unforgettable German word for
memory management: speicherverwaltung. 
 
> Question:  the error reported,  is the issue clear and is there a solution
> ?     (i'm not a 'c' or expert coder or familiar with clisp code, so  I
> dont know what to make of it).

This one:

../src/lispbibl.d:7598:15: error: size of array ‘symbol_size_check’ is negative
 7598 |   typedef int symbol_size_check[1 - 2 * (int)(sizeof(symbol_) % varobject_alignment)];
      |  　            ^~~~~~~~~~~~~~~~~

is using an array declaration hack to implement a compile time sanity check:

  typedef int size_check[1 - 2 * CONSTANT_EXPR_THAT_MUST_BE_ZERO]

If CONSTANT_EXPR_THAT_MUST_BE_ZERO is nonzero, size_check is declared
as an array type with a negative dimension, violating an ISO C constraint,
requiring a diagnostic. Most compilers will treat that as a fatal error,
aborting compilation.

In this case, the expression that must be zero is checking that
the sizeof the type symbol_ is a multiple of varobject_alignment.

That not being the case is pointing to some inconsistency in
the configuration: a mismatch between how the content of symbol_
is defined relative to how varobject_alignment is defined.


In addition, the following is probably okay, but could benefit from
modernization:

../src/spvw.d:968:3: warning: ignoring return value of ‘__builtin_alloca’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  968 |   alloca(1);                    /* Makes this function non-inlinable. */
      |   ^~~~~~~~~~~~~~~~~~~
make: *** [Makefile:1133: spvw.o] Error 1

E.g. define a "notinline" macro like this:

#if __GNUC__
#define noinline __attribute__((noinline))
#else
#define noinline
#endif

notinline void my_function_that_should_not_be_inlined(void)
{
   ...
}

The compiler is noticing that the return value of alloca(1) isn't
being captured and would be justified in optimizing it away,
subsequently allowing the function to be inlined.

[clisp-list] compile on i686 issue for advice/comment please

[C H. <bum...@gm...>]

Hello clisp-list

Trying to compile latest clisp  ( that checked out from the master branch
on gitlab).
The computer (laptop) is a [old] linux 32bit  celeron M 440  (slackware).

All dependencies present (i think).

The problem seems to be when using the flag, --with-threads=POSIX_THREADS
as without it, all compiles through.

With the flag the build bails out at 'configure' time.

Question [firstly I suppose]:  does 'threads' only work on  64 bit arch,
because there seems to be no trouble on 64 bit arch   ?

If the above is a 'yes', then no need to go further perhaps.

Question:  what is spvw.'x'  (.d .c etc)  doing and why is it an issue on
32 bit arch ?

Question:  the error reported,  is the issue clear and is there a solution
?     (i'm not a 'c' or expert coder or familiar with clisp code, so  I
dont know what to make of it).

Thank you
Habs


file attached (if it works) ...

the line at the top is the 'configure' attempted  (actually it is a
stripped down of modules one than initially tried ).

the rest is where the 'configure' bailed out.

[clisp-list] Cross-function tail calls?

[Kaz K. <ka...@ky...>]

Hi all,

I seem to remember that CLISP only has tail call optimization for self-calls.

Recently I did work on TCO for TXR Lisp. In a first milestone, I made self TCO work,
where a backwards JMP instruction is at the core.

In the current release, I also made cross-call TCO work. I wonder whether a similar
technique could work for CLISP.

I came up with a trick: I added a prefix instruction called TAIL to the VM. The prefix
instruction is inserted before one of several types of fuction calling instructions
that were identified by the compiler as being in a tail position.

The VM can then perform a modified function call (if the target function is a VM
function). whereby it allocates the callee's frame in the same space as the
caller.

If the caller needs more space, I alloca() the difference. Some trickery is used to
propagate the arguments. They have to be prepared while the old stack frame is
still valid, and then be available to the new frame after the old one is overwritten.

It's possible to ignore the TAIL instruction as a no-op and everything will work,
minus the tail semantics.

Re: [clisp-list] make install fails: #error "Please include config.h first."

[Stephen B. <ste...@gm...>]

On Sat, 02 Nov 2024 19:38:06 +0100 Stephen Berman via clisp-list <cli...@li...> wrote:

> Today I updated my local git repo of clisp to the latest commit
> 0e67ff47e and successfully configured and built clisp, but install
> failed with many errors like this (I've attached a file with the full
> shell output of make install):
>
> In file included from /usr/include/string.h:462,
>                  from /home/steve/src/clisp/build_20241102/gllib/string.h:41,
>                  from clisp.c:23:
> /home/steve/src/clisp/build_20241102/gllib/strings.h:42:3: error: #error "Please include config.h first."
>    42 |  #error "Please include config.h first."
>       |   ^~~~~
>
> A web search found many reports with this error, but I could not find
> anything that made make install succeed.  My system is GNU/Linux with
> gcc-14.2.0 and glibc-2.40.  My last build of clisp, where make install
> also succeeded, was last May 21, using the latest git commit at that
> time; that system was with gcc-13.2.0 and glibc-2.39.
>
> I'd be grateful for any help in solving this issue.

I just updated again and now make install succeeded too.  Perhaps the
problem I had yesterday was fixed by this commit?

* 79d82fcb6..: Bruno Haible 2024-11-03 build: Build the clisp driver program without gnulib, part 2.

Steve Berman

Re: [clisp-list] make install fails: #error "Please include config.h first."

[Stephen B. <ste...@gm...>]

On Sat, 02 Nov 2024 19:38:06 +0100 Stephen Berman <ste...@gm...> wrote:

> Today I updated my local git repo of clisp to the latest commit
> 0e67ff47e and successfully configured and built clisp, but install
> failed with many errors like this (I've attached a file with the full
> shell output of make install):

Apparently the list server deleted the attachment; I can post the full
output inline if desired.

Steve Berman

[clisp-list] make install fails: #error "Please include config.h first."

[Stephen B. <ste...@gm...>]

Today I updated my local git repo of clisp to the latest commit
0e67ff47e and successfully configured and built clisp, but install
failed with many errors like this (I've attached a file with the full
shell output of make install):

In file included from /usr/include/string.h:462,
                 from /home/steve/src/clisp/build_20241102/gllib/string.h:41,
                 from clisp.c:23:
/home/steve/src/clisp/build_20241102/gllib/strings.h:42:3: error: #error "Please include config.h first."
   42 |  #error "Please include config.h first."
      |   ^~~~~

A web search found many reports with this error, but I could not find
anything that made make install succeed.  My system is GNU/Linux with
gcc-14.2.0 and glibc-2.40.  My last build of clisp, where make install
also succeeded, was last May 21, using the latest git commit at that
time; that system was with gcc-13.2.0 and glibc-2.39.

I'd be grateful for any help in solving this issue.

Steve Berman

Re: [clisp-list] array limits on arm ampere

[C H. <bum...@gm...>]

I get the same issue on a laptop (hp probook).

it seems that 4194303  is the max. I found possible using the OP code.

Habs


On Wed, 24 Jan 2024 at 23:32, Don Cohen <
don...@is...> wrote:

>
> I've recently started using oracle cloud and I
> notice that I can't allocate an array of >= 4M characters.
>
> On intel with
>  *features*
> (:REGEXP :WILDCARD :SYSCALLS :I18N :LOOP :COMPILER :CLOS :MOP :CLISP
> :ANSI-CL
>  :COMMON-LISP :LISP=CL :INTERPRETER :LOGICAL-PATHNAMES :MT :SOCKETS
>  :GENERIC-STREAMS :FFI :GETTEXT :UNICODE :BASE-CHAR=CHARACTER :WORD-SIZE=64
>  :PC386 :UNIX)
> (length (make-array  (* 1024 1024 4)
>         :element-type 'character
>         :fill-pointer t :adjustable t))
> => 4194304
>
> but on ampere with
> *features*
> (:READLINE :REGEXP :WILDCARD :SYSCALLS :I18N :LOOP :COMPILER :CLOS :MOP
> :CLISP
>  :ANSI-CL :COMMON-LISP :LISP=CL :INTERPRETER :LOGICAL-PATHNAMES :SOCKETS
>  :GENERIC-STREAMS :SCREEN :FFI :GETTEXT :UNICODE :BASE-CHAR=CHARACTER
>  :WORD-SIZE=64 :UNIX)
> *** - string too long: desired length 4194304 exceeds the supported
> maximum length
>
> Both say
> array-dimension-limit
> 4294967296
> (interestingly, one MORE than impnotes says should be the value
> for a 64 bit cpu)
>
>
> _______________________________________________
> clisp-list mailing list
> cli...@li...
> https://lists.sourceforge.net/lists/listinfo/clisp-list
>

[clisp-list] array limits on arm ampere

[<don...@is...>]

I've recently started using oracle cloud and I
notice that I can't allocate an array of >= 4M characters.

On intel with
 *features*
(:REGEXP :WILDCARD :SYSCALLS :I18N :LOOP :COMPILER :CLOS :MOP :CLISP :ANSI-CL
 :COMMON-LISP :LISP=CL :INTERPRETER :LOGICAL-PATHNAMES :MT :SOCKETS
 :GENERIC-STREAMS :FFI :GETTEXT :UNICODE :BASE-CHAR=CHARACTER :WORD-SIZE=64
 :PC386 :UNIX)
(length (make-array  (* 1024 1024 4)
        :element-type 'character
        :fill-pointer t :adjustable t))
=> 4194304

but on ampere with
*features*
(:READLINE :REGEXP :WILDCARD :SYSCALLS :I18N :LOOP :COMPILER :CLOS :MOP :CLISP
 :ANSI-CL :COMMON-LISP :LISP=CL :INTERPRETER :LOGICAL-PATHNAMES :SOCKETS
 :GENERIC-STREAMS :SCREEN :FFI :GETTEXT :UNICODE :BASE-CHAR=CHARACTER
 :WORD-SIZE=64 :UNIX)
*** - string too long: desired length 4194304 exceeds the supported maximum length

Both say
array-dimension-limit
4294967296
(interestingly, one MORE than impnotes says should be the value
for a 64 bit cpu)

Re: [clisp-list] Mildly amusing diagnostic wording.

[Pascal B. <pj...@in...>]

> On 8 Nov 2023, at 08:07, Kaz Kylheku <ka...@ky...> wrote:
> 
> [1]> (loop (loop-finish)) 
> 
> *** - (LOOP-FINISH) is possible only from within LOOP
> The following restarts are available:
> ABORT :R1 Abort main loop 
> 
> :)
> 

This is an error in the error message. (issue a bug report)
The LOOP operator introduces two kinds of loops:
- simple loops as the one you wrote,
- extended loops.

LOOP-FINISH is only available in extended loops, not in simple loops.

If you want to use loop-finish, you may add a do keyword to make it an extended loop:
(loop do (loop-finish))


-- 
__Pascal J. Bourguignon__

[clisp-list] Mildly amusing diagnostic wording.

[Kaz K. <ka...@ky...>]

[1]> (loop (loop-finish)) 

*** - (LOOP-FINISH) is possible only from within LOOP
The following restarts are available:
ABORT :R1 Abort main loop 

:)

Re: [clisp-list] clisp on gitlab

[Erik A. <aue...@un...>]

Hi,

On 23.07.23 02:20, Raymond Toy wrote:
> FYI, clisp is now on gitlab, not sourceforge: 
> https://gitlab.com/gnu-clisp/clisp and the last change was 4 days ago.
> 
> I didn't know this until I was just setting up gmane on thunderbird and 
> read the clisp list there.
Thanks for this information!

The CLISP web page still does not mention GitLab, only SourceForge.
I've checked "http://clisp.org", "https://clisp.sourceforge.io/",
and "https://www.gnu.org/software/clisp/" right now.

It would be great if the CLISP project would update this information.
Thanks in advance!

Best regards,
Erik

Re: [clisp-list] clisp on gitlab

[Raymond T. <toy...@gm...>]

On 7/22/23 5:20 PM, Raymond Toy wrote:
> FYI, clisp is now on gitlab, not sourceforge: 
> https://gitlab.com/gnu-clisp/clisp and the last change was 4 days ago.
>
> I didn't know this until I was just setting up gmane on thunderbird 
> and read the clisp list there.
>
Oops.  Wrong to address.

[clisp-list] clisp on gitlab

[Raymond T. <toy...@gm...>]

FYI, clisp is now on gitlab, not sourceforge: 
https://gitlab.com/gnu-clisp/clisp and the last change was 4 days ago.

I didn't know this until I was just setting up gmane on thunderbird and 
read the clisp list there.

Re: [clisp-list] unwanted new line

[Sam S. <sd...@gn...>]

> * Don Cohen <qba...@vf...> [2023-07-14 02:15:04 +0000]:
>
> (setf list '("abc" "def" "qwe
> rty
> uiop" "zxc"))
>
> (with-output-to-string (s)(loop for x in list do (format s "~s~c" x #\tab)))
> "\"abc\"        \"def\"
> \"qwe
> rty
> uiop\"  \"zxc\" "
>
> Why is there an extra new line before the list element that contains
> the newlines?
> Is there some way to suppress it ?

https://clisp.sourceforge.io/impnotes/faq.html#faq-pp-newline
;-)
https://clisp.sourceforge.io/impnotes/faq.html#faq-fine



-- 
Sam Steingold (https://aphar.dreamwidth.org/) on Pop 22.04 (jammy) X 11.0.12101004
https://lastingimpactpsychology.com https://steingoldpsychology.com
https://thereligionofpeace.com https://camera.org https://honestreporting.com
Booze is the answer. I can't remember the question.

[clisp-list] unwanted new line -- never mind

[<don...@is...>]

I see I asked the same question in 2016 !!
And the answer is the same now -- print-pretty is t


Don Cohen writes:
 > 
 > (setf list '("abc" "def" "qwe
 > rty
 > uiop" "zxc"))
 > 
 > (with-output-to-string (s)(loop for x in list do (format s "~s~c" x #\tab)))
 > "\"abc\"        \"def\"
 > \"qwe
 > rty
 > uiop\"  \"zxc\" "
 > 
 > Why is there an extra new line before the list element that contains
 > the newlines?
 > Is there some way to suppress it ?

[clisp-list] unwanted new line

[<don...@is...>]

(setf list '("abc" "def" "qwe
rty
uiop" "zxc"))

(with-output-to-string (s)(loop for x in list do (format s "~s~c" x #\tab)))
"\"abc\"        \"def\"
\"qwe
rty
uiop\"  \"zxc\" "

Why is there an extra new line before the list element that contains
the newlines?
Is there some way to suppress it ?

[clisp-list] clisp.org points to SourceForge, not GitLab

[Erik A. <aue...@un...>]

Hi,

it seems to me as if the clisp.org (and www.gnu.org/software/clisp) site
show outdated information by only mentioning the SourceForge Mercurial
repository and the SourceForge bug tracker.  Bug reports are directed
to the SourceForge bug tracker, neither to a mailing list nor the GitLab
issue tracker.

It seems to me as if this is no longer good advice, and perhaps it might
be helpful to update those web pages.

(I tried to report a bug and followed the directions from clisp.org to
add it to the SourceForge bug tracker.  I did not receive any reply,
so I do not know if it has been seen.  I have seen another recent bug
report there, which might have been overlooked, but I do not know that.)

Kind regards,
Erik
-- 
A distributed system is one in which the failure of a computer you didn't
even know existed can render your own computer unusable.
                        -- Leslie Lamport

Re: [clisp-list] FYI: Cygwin package is crippled: no FFI.

[Ken B. <kb...@co...>]

On 1/12/2023 3:03 AM, Kaz Kylheku wrote:
> Hi All,
> 
> Just a heads up that whoever is maintaining the CLISP
> package for Cygwin seems not to have built it with
> FFI support.
> 
> The FFI package doesn't exist.
> 
> I'm trying to use an old program of mine, and oops!

This belongs on the Cygwin list.  I'll follow up there.

Ken

[clisp-list] FYI: Cygwin package is crippled: no FFI.

[Kaz K. <ka...@ky...>]

Hi All, 

Just a heads up that whoever is maintaining the CLISP
package for Cygwin seems not to have built it with
FFI support.

The FFI package doesn't exist. 

I'm trying to use an old program of mine, and oops!

[clisp-list] [CfP] ELS 2023, 16th European Lisp Symposium, April 24-25, Amsterdam

[Didier V. <di...@lr...>]

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
		     16th European Lisp Symposium

			   Call for Papers

			  April 24-25, 2023
		Startup Village, Amsterdam, Nederlands

	     https://www.european-lisp-symposium.org/2023

		     Sponsored by EPITA and DIRO
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Important Dates
~~~~~~~~~~~~~~~
- Submission deadline: February 26, 2023
- Author notification: March    26, 2023
- Final papers due:    April     9, 2023
- Symposium:           April 24-25, 2023


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: technical papers of up to 8 pages that describe original
  results or explain known ideas in new and elegant ways.

* 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.

All submissions should be formatted following the ACM SIGS guidelines
and include ACM Computing Classification System 2012 concepts and
terms. Submissions should be uploaded to Easy Chair, at the following
link http://www.easychair.org/conferences/?conf=els2023.

Note: to help us with the review process please indicate the type of
submission by entering either "paper", "demo", or "tutorial" in the
Keywords field.


Programme Chair
~~~~~~~~~~~~~~~
Stefan Monnier, DIRO, Université de Montréal Canada

Programme Committee
~~~~~~~~~~~~~~~~~~~
TBA


Local Chair
~~~~~~~~~~~
Breanndán Ó Nualláin, Machine Learning Programs, Nederlands

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info

[clisp-list] [CfPart] ELS 2022, 15th European Lisp Symposium, March 21-22, Porto.

[Didier V. <di...@lr...>]

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
		     15th European Lisp Symposium

			Call for Participation

			  March 21-22, 2022
		    FEUP, Porto, Portugal & Online
		   In cooperation with ACM SIGPLAN

	     https://www.european-lisp-symposium.org/2022

	      Sponsored by EPITA, Franz Inc., and SISCOG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Important News
~~~~~~~~~~~~~~~
- Full programme now online
- Invited speakers below
- Registrations are open


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


Invited talks
~~~~~~~~~~~~~
Building SICMUtils, the Atelier of Abstractions -- Sam Ritchie

SICMUtils is a Clojure library designed for interactive exploration of
mathematical physics. It is simultaneously a work of persuasive
writing, a collection of essays on functional pearls and computational
ideas, a stable of workhorse functional abstractions, and a practical
place to work and visualize algorithms and physical systems, on a
server or in the browser.

How do you build a library like this? This talk will go through the
architecture of SICMUtils, based on many of the ideas of "additive
programming" from Gerald Sussman and Chris Hanson's latest book,
Software Design for Flexibility. We'll look at surprising examples of
the system becoming easier to extend over time. Clojure's embrace of
its host platform lets us use the best modern work in Javascript for
visualization, while keeping the horsepower of our servers for real
work. Lisp's particular elegance will shine throughout.


Creating a Common Lisp Implementation -- Robert Strandh

Being dissatisfied with the way current Common Lisp implementations
are written, and with the duplication of system code between different
implementations, we started the SICL project in 2008. The initial idea
was to create modules that the creators of Common Lisp implementations
could use to create a complete system from an initial minimal core.
But this idea was unsatisfactory because it required each module to be
written in a subset of Common Lisp. So instead, we decided to use the
full language to implement these modules, effectively making them
useless to an implementation using traditional bootstrapping
techniques. We therefore decided to also create a new Common Lisp
implementation (also named SICL), that could use those modules.

A crucial element is a bootstrapping technique that can handle these
modules. In this spirit, we have developed several modules, including
an implementation of CLOS which is also an important element of
bootstrapping. Lately, we have increased our level of ambition in that
we want to extract those modules as separate (and separately
maintained) repositories, which requires us to deal with code during
bootstrapping that was not specifically written for SICL.

In our talk, we describe this evolution of ambition, and its
consequences to bootstrapping, in more detail. We also give an
overview of several new techniques we created, some of which have been
published (at ICL and ELS) and some of which have not. Finally, we
discuss the future of the project, and other projects for which we
imagine SICL to be a base.


Lisp as Renaissance Workshop: A Lispy Tour through Mathematical
Physics -- Sam Ritchie

Lisp is an exquisite medium for the communication of computational
ideas. From our most accurate observations of physical reality up
through chemistry, biology, and cognition, the universe seems to be
computing itself; modeling and simulating these systems in machines
has led to incredible technological wealth.

Deep principles and beautiful abstractions seem to drive these
systems, but they have always been hard to discover; and we are
floundering at the computational frontiers of intelligence, synthetic
biology and control systems for our climate. The only way to push
forward is to build powerful tools that can communicate and teach.

This talk will take a tour through SICMUtils, a Lisp system designed
as a workshop for conducting serious work in mathematical physics and
sharing those explorations in a deeply interactive, multiplayer way.
The library’s growth parallels our human scientific history; hopefully
tools like this will help us write the next chapter.



Programme Chair
~~~~~~~~~~~~~~~
Jim Newton - EPITA Research Lab (LRDE), France

Programme Committee
~~~~~~~~~~~~~~~~~~~
Philipp Meier, Nubank
Ioanna M. Dimitriou H., Igalia
Mikhail Raskin, Technical University of Munich
Nick Levine, RavenPack
Adrien Pommellet, LRDE, EPITA
Marco Heisig, Friedrich-Alexander-Universität Erlangen
Alberto Riva, Bioinformatics Core, ICBR, University of Florida
Marco Antoniotti, DISCo, Università degli Studi di Milano-Bicocca
Nicolas Neuss, Friedrich-Alexander-Universität Erlangen
Christophe Rhodes, Google UK
Irène Anne Durand, LaBRI, University of Bordeaux
Ralf Moeller
Breanndán Ó Nualláino, University of Amsterdam
Marc Battyani, Fractal Concept
Pascal Costanza, Intel
Sky Hester, Private Consultant

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info

[clisp-list] [Extended Deadline] 15th European Lisp Symposium

[Didier V. <di...@lr...>]

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
		     15th European Lisp Symposium

			   Call for Papers

			  March 21-22, 2022
		    FEUP, Porto, Portugal & Online
		  In co-location with <Programming>

	     https://www.european-lisp-symposium.org/2022

		  Sponsored by EPITA and Franz Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Important Dates
~~~~~~~~~~~~~~~
- Submission deadline ***EXTENDED***: January  30, 2022
- Author notification: February 21, 2022
- Final papers due:    March     7, 2022
- Symposium:           March 21-22, 2022


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: technical papers of up to 8 pages that describe original
  results or explain known ideas in new and elegant ways.

* 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.

All submissions should be formatted following the ACM SIGS guidelines
and include ACM Computing Classification System 2012 concepts and
terms. Submissions should be uploaded to Easy Chair, at the following
link http://www.easychair.org/conferences/?conf=els2022.

Note: to help us with the review process please indicate the type of
submission by entering either "paper", "demo", or "tutorial" in the
Keywords field.


Programme Chair
~~~~~~~~~~~~~~~
Jim Newton - EPITA Research Lab (LRDE), France

Programme Committee
~~~~~~~~~~~~~~~~~~~
Philipp Meier, Nubank
Ioanna M. Dimitriou H., Igalia
Mikhail Raskin, Technical University of Munich
Nick Levine, RavenPack
Adrien Pommellet, LRDE, EPITA
Marco Heisig, FAU Erlangen-Nürnberg
Alberto Riva, Bioinformatics Core, ICBR, University of Florida
Marco Antoniotti, DISCo, Università degli Studi di Milano-Bicocca
Nicolas Neuss, Friedrich-Alexander-Universität Erlangen
Christophe Rhodes, Google
Irène Anne Durand, LaBRI, University of Bordeaux
Ralf Moeller
Breanndán Ó Nualláino, University of Amsterdam
Marc Battyani, Fractal Concept
Pascal Costanza, Intel

-- 
Didier Verna <di...@el...>
ELS Steering Committee

[clisp-list] [Last CfP] 15th European Lisp Symposium, March 21-22 2022, Porto

[Didier V. <di...@lr...>]

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
		     15th European Lisp Symposium

			   Call for Papers

			  March 21-22, 2022
		    FEUP, Porto, Portugal & Online
		  In co-location with <Programming>

	     https://www.european-lisp-symposium.org/2022

		  Sponsored by EPITA and Franz Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Important Dates
~~~~~~~~~~~~~~~
- Submission deadline: January  23, 2022
- Author notification: February 21, 2022
- Final papers due:    March     7, 2022
- Symposium:           March 21-22, 2022


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: technical papers of up to 8 pages that describe original
  results or explain known ideas in new and elegant ways.

* 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.

All submissions should be formatted following the ACM SIGS guidelines
and include ACM Computing Classification System 2012 concepts and
terms. Submissions should be uploaded to Easy Chair, at the following
link http://www.easychair.org/conferences/?conf=els2021.

Note: to help us with the review process please indicate the type of
submission by entering either "paper", "demo", or "tutorial" in the
Keywords field.


Programme Chair
~~~~~~~~~~~~~~~
Jim Newton - EPITA Research Lab, France

Programme Committee
~~~~~~~~~~~~~~~~~~~
Philipp Meier, Nubank
Ioanna M. Dimitriou H., Igalia
Mikhail Raskin, Technical University of Munich
Nick Levine, RavenPack
Adrien Pommellet, EPITA Research Lab
Marco Heisig, FAU Erlangen-Nürnberg
Alberto Riva, Bioinformatics Core, ICBR, University of Florida
Marco Antoniotti, DISCo, Università degli Studi di Milano-Bicocca
Nicolas Neuss, Friedrich-Alexander-Universität Erlangen
Christophe Rhodes, Google
Irène Anne Durand, LaBRI University of Bordeaux
Ralf Moeller
Breanndán Ó Nualláin
Marc Battyani, Fractal Concept
Pascal Costanza, Intel, Belgium


-- 
Didier Verna

[clisp-list] [CfP] 15th European Lisp Symposium, March 21-22 2022, Porto, Portugal

[Didier V. <di...@lr...>]

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
		     15th European Lisp Symposium

			   Call for Papers

			  March 21-22, 2022
		    FEUP, Porto, Portugal & Online
		  In co-location with <Programming>

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

			  Sponsored by EPITA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Important Dates
~~~~~~~~~~~~~~~
- Submission deadline: January  23, 2022
- Author notification: February 21, 2022
- Final papers due:    March     7, 2022
- Symposium:           March 21-22, 2022


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: Technical papers of up to 8 pages that describe original
  results or explain known ideas in new and elegant ways.

* 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.

All submissions should be formatted following the ACM SIGS guidelines
and include ACM Computing Classification System 2012 concepts and
terms. Submissions should be uploaded to Easy Chair, at the following
http://www.easychair.org/conferences/?conf=els2021

Note: to help us with the review process please indicate the type of
submission by entering either "paper", "demo", or "tutorial" in the
Keywords field.


Programme Chair
~~~~~~~~~~~~~~~
Jim Newton - EPITA Research Lab (LRDE), France

Programme Committee
~~~~~~~~~~~~~~~~~~~
tba

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info