January 2017 - ecl-devel - mailman3.common-lisp.net

EQL5: QML/Lisp bridge (for desktop)
by PR 19 Jan '17

19 Jan '17

For those interested in the progress of EQL5: Two new modules have been added lately: "multimedia" and "quick". The most interesting part is the QML / Lisp bridge, which allows creating applications using only QML (declarative UI) and Lisp (instead of JavaScript). For examples of calling Lisp from QML, see: https://gitlab.com/eql/EQL5/blob/master/examples/M-modules/quick/qml-lisp/q… For a working example (port of the QtQuick1 "Tic-Tac-Toe" example), see: QML: https://gitlab.com/eql/EQL5/blob/master/examples/M-modules/quick/Tic-Tac-To… Lisp: https://gitlab.com/eql/EQL5/blob/master/examples/M-modules/quick/Tic-Tac-To… This is meant for desktop applications only (I don't have any experience with mobile apps, and don't know the current state of the android port). Paul

1 0

Continuous integration
by Roger Sen Montero 05 Jan '17

05 Jan '17

Hi, Any plan to deploy Gitlab continuous integration? If yes, happy to contribute with a mac for testing. -- Roger Sen Montero roger.sen(a)gmail.com +34 649 975 570

2 3

[CfP] ELS'17, 10th European Lisp Symposium, April 3-4 2017, Brussels
by Didier Verna 03 Jan '17

03 Jan '17

ELS'17 - 10th European Lisp Symposium VUB - Vrije Universiteit Brussel Belgium April 3-4, 2017 In co-location with <Programming> 2017 Sponsored by Brunner Software GmbH http://www.european-lisp-symposium.org/ The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp and Lisp-inspired dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, Hop and so on. We encourage everyone interested in Lisp to participate. The 10th 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 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 2 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. The symposium will also provide slots for lightning talks, to be registered on-site every day. All submissions should be formatted following the ACM SIGS guidelines and include ACM classification categories and terms. For more information on the submission guidelines and the ACM keywords, see: http://www.acm.org/sigs/publications/proceedings-templates and http://www.acm.org/about/class/1998. The conference proceedings will be published in the ACM Digital Library. Submissions should be uploaded to Easy Chair, at the following address: https://www.easychair.org/conferences/?conf=els17 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. Important dates: - 30 Jan 2017 Submission deadline - 27 Feb 2017 Notification of acceptance - 20 Mar 2017 Final papers due - 03-04 Apr 2017 Symposium Programme chair: Alberto Riva, University of Florida, USA Programme committee: Marco Antoniotti, Università Milano Bicocca, Italy Marc Battyani, FractalConcept Theo D'Hondt, Vrije Universiteit Brussel, Belgium Marc Feeley, Université de Montreal, Canada Stelian Ionescu, Google Rainer Joswig, Independent Consultant, Germany António Menezes Leitão, Technical University of Lisbon, Portugal Nick Levine, RavenPack Henry Lieberman, MIT, USA Mark Tarver, Shen Programming Group Jay McCarthy, University of Massachusetts Lowell, USA Christian Queinnec, Université Pierre et Marie Curie, France François-René Rideau, Bridgewater Associates, USA Nikodemus Siivola, ZenRobotics Ltd Alessio Stalla, Università degli Studi di Genova, Italy Search Keywords: #els2017, ELS 2017, ELS '17, European Lisp Symposium 2017, European Lisp Symposium '17, 10th ELS, 10th European Lisp Symposium, European Lisp Conference 2017, European Lisp Conference '17 -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info

1 0

Feature request: dlopen(NULL, ...
by Michael Fox 02 Jan '17

02 Jan '17

I was wondering if I could get some feeback on an ECL feature request that I posted here: https://gitlab.com/embeddable-common-lisp/ecl/issues/336 <https://gitlab.com/embeddable-common-lisp/ecl/issues/336> Here is the text: I would like to be able to call functions using dynamic FFI in the program into which ECL has been embedded. In Linux, you can do this by calling `dlopen` with `NULL` for the filename. > If filename is NULL, then the returned handle is for the main program. http://man7.org/linux/man-pages/man3/dlopen.3.html Looking at ECL source code, it does not seem to be supported. `dlopen` is called in `c/ffi/libraries.d` like this: char *filename_string = (char*)filename->base_string.self; #ifdef HAVE_DLFCN_H block->cblock.handle = dlopen(filename_string, RTLD_NOW|RTLD_GLOBAL); So, I guess there's no way to set `filename_string = NULL`. One way to do it would be to say if you call (ffi:load-foreign-library "") Then it will skip the checks to see if the file exists and just call `dlopen(NULL, ...` Another way would be to make a new function `ffi:load-main-program`. I don't have any suggestions as to which would be better as I am very new to Lisp. Thank you for your attention.

2 1

ECL does not support docstrings for functions created with flet, labels or lambda. Why?
by Alexander Artemenko 02 Jan '17

02 Jan '17

Hi! I found that: CL-USER> (let ((foo (lambda () "With docstring" 100500))) > (princ (funcall foo)) > (terpri) > (princ (documentation foo t))) > 100500 > NIL > NIL in ECL, but: CL-USER> (let ((foo (lambda () "With docstring" 100500))) > (princ (funcall foo)) > (terpri) > (princ (documentation foo t))) > 100500 > With docstring > "With docstring" Why? BTW, similar behaviour have ABCL, Allegro and CCL. But SBCL and CLISP work as expected. -- Alexander Artemenko (a.k.a. Svetlyak 40wt) Blog: http://dev.svetlyak.ru

2 1