ecl-devel

ecl-devel@common-lisp.net

1 participants
232 discussions

[Last CfP] 15th European Lisp Symposium, March 21-22 2022, Porto
by Didier Verna 11 Jan '22

11 Jan '22

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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

1 0

Considering resignation as maintainer
by Robert Goldman 10 Jan '22

10 Jan '22

I have discovered that Stas Bokuraev is continuing to refuse to update Edi packages to modern ASDF system-naming. This would not be bad in and of itself, because these are open source systems, and they can be forked. What *is* bad is that he has publicly stated that he is doing this hoping that the resulting warnings will break people's systems and thus cause them to get angry and complain to me about ASDF checking system names. What is even worse is that the CL community tacitly accepts this as normal behavior. I would like to see the CL open source community pause and consider what constitutes a healthy community. I don't believe that someone trying to break things in order to pressure a volunteer maintainer of infrastructure is something that a healthy community should accept. If the community prefers a more rough-and-tumble approach, I can accept that, but if so it's time for the community to find an ASDF maintainer who is more in harmony with the values it (at least implicitly) espouses.

2 1

manual typo
by James Cloos 23 Dec '21

23 Dec '21

At: https://common-lisp.net/project/ecl/static/manual/Characters.html#Characters it looks like the tabe has the 'With Unicode' and 'Without Unicode' entries backwards. -JimC -- James Cloos <cloos(a)jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6

2 1

[CfP] 15th European Lisp Symposium, March 21-22 2022, Porto, Portugal
by Didier Verna 20 Oct '21

20 Oct '21

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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

1 0

Re: Re: How to use lisp packages from libraries?
by Иван Трусков 06 Jul '21

06 Jul '21

Thanks for your explanation! I have changed lisp code to have package definition and in-package declaration, and after that everything did work (also, i per your advice used package name in symbol lookup in C code). There is one thing i would like to discuss a little bit further. >The question you need to answer is whether you want your program defer >to run-time, on the user's workstation, when to use quicklisp to > donwload and install the "str" system, and load it into your program > to get the "STR" package and its functions? Do you realize that every > month, new systems are added to quicklisp, but also SOME SYSTEMS are > REMOVED from the quicklisp distribution!? Do you want your program to > break next month because the quicklisp maintainer decided to remove > some depdency from its distribution? 1) packages changing in repository is, well, just the fact of life. In most cases hoping for the best is enough. I mean, there is no certain guarantee that digital infrastructure taken for granted will be there tomorrow? 2) what i am really curious about is: when my lisp package is compiled, let us say, monolithically - is used package "pulled into" it? In resulting object fdile, is there all the machine code corresponding to the functions from it that i have used? Maybe to other ones?

1 0

How to use lisp packages from libraries?
by Иван Трусков 05 Jul '21

05 Jul '21

I am trying to use a package function in my lisp library that will later be called from a C application. To be precise, it is shorten function from the str package. Here is my lisp library text: ;; (require :str) ;; (use-package :str) (defun echo-string (s) (coerce (format nil "Recieved input: ~10A" (shorten-string s)) 'base-string)) (defun shorten-string (s) (declare (string s)) (let ((l (length s))) (if (> l 10) (concat (shorten 7 s) (substring (- l 3) nil s)) s))) First lines are commented out because i do not know their necessity in the library. That's part of the question. However, all i get when trying to use any function from this library is a number of undecipherable errors, like this: https://pastebin.com/Sn8jgE9f Here is my C code for a minimal case: #include <stdlib.h> #include <stdio.h> #include <ecl/ecl.h> // utility functions cl_object make_cl_string(const char * pstring) { return ecl_make_constant_base_string(pstring, strlen(pstring)); } int main(int argc, const char* argv[]) { /* Initialize ECL */ ecl_set_option(ECL_OPT_TRAP_SIGSEGV, false); cl_boot(argc, argv); extern void init_lib_ASDF(cl_object); ecl_init_module(NULL, init_lib_ASDF); // is this necessary? extern void init_lib_ECL_QUICKLISP(cl_object); ecl_init_module(NULL, init_lib_ECL_QUICKLISP); cl_object ecl_module_name = make_cl_string("ecl-quicklisp"); cl_require(1, ecl_module_name); cl_object str_module_name = make_cl_string("str"); cl_require(1, str_module_name); // this code fails, not clear what use as package designator /* cl_object str_package_name = make_cl_string(":str"); */ /* cl_use_package(1, str_package_name); */ extern void init_embedded_console(cl_object); ecl_init_module(NULL, init_embedded_console); // library calls cl_object fname = make_cl_string("ECHO-STRING"); cl_object echo_func = cl_find_symbol(1, fname); assert(ECL_SYMBOLP(pstate->echo_func)); const char * line = "hello"; cl_object call_result = cl_funcall(2, echo_func, make_cl_string(line)); char * msg_str = malloc(call_result->string.fillp + 1); memcpy(msg_str, call_result->string.self, call_result->string.fillp + 1); printf("Output: %s\n", msg_str); free(msg_str); const char * line2 = "hello"; call_result = cl_funcall(2, echo_func, make_cl_string(line2)); msg_str = malloc(call_result->string.fillp + 1); memcpy(msg_str, call_result->string.self, call_result->string.fillp + 1); printf("Output: %s\n", msg_str); free(msg_str); return 0; } What should be done for me to be able to use some package (installed with quicklisp) from my ECL library? How should the initialisation be done?

2 1

ASDF 3.3.5 is released
by Robert Goldman 03 Jul '21

03 Jul '21

Please consider upgrading the version you are distributing with your implementation. Note that this is strictly a bug fix release so should not cause issues in upgrading. But "should" -- software is unpredictable. Announcement email follows. Best, R

1 0

Flags for other platforms during static lib compilation?
by Joshua Armenta 29 Jun '21

29 Jun '21

Is there a flag to set another architecture type during the compilation process? For example I’m on an Intel Mac but I want to make a project build for ARM Mac (or a fat binary) to not use Rosetta 2 for that version. Or, I’m on a Mac but want to cross compile the lisp project/static library to windows. Trying to integrate some code into a CI platform. Thx! Sent from my iPhone Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.

2 3

Ignore build break on Raspberry Pi
by dave＠synergy.org 10 Jun '21

10 Jun '21

Operator error.

1 0

Build error on Raspberry Pi
by dave＠synergy.org 10 Jun '21

10 Jun '21

It's been quite a while since I re-built ecl on my Pi. Dave

1 0

← Newer
1
2
3
4
5
6
7
...
24
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

ecl-devel