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

Conflicts when starting up various processes
by Diogo Franco 05 Feb '16

05 Feb '16

Hi, We have a few different c++ projects with ecl embedded, which when starting up, have ecl compiling and loading quite a bit of lisp code. If we start the various processes close enough in time, conflicts occur while compiling the lisp code. All is good if I wait for the lisp compilations between starting each process, but this is troublesome to do in production. We believe this may be because the different processes might be using the same temporary folder for the compiled code or something of this nature. Is there any way to set the temporary path where ecl builds source code? Or some other hint you think might help? Many thanks in advance for your help, Diogo Franco

2 2

ld-flags on win
by Fabrizio Fabbri 30 Jan '16

30 Jan '16

Hi all, I'm on my win64 build and I'm using asdf to define my system but with asdf:make-build or asdf:load-bundle-op the ld-flags option to link some additional static library to my fasl is not passed to the linker. So far I workaround with (si:setenv "_CL_" "bla bla bla") but it's not ideal. Am I doing something wrong or is a know issue? Kindest regards. bix P.S. ECL is so fun. Great job.

2 1

Help on unit test
by Fabrizio Fabbri 30 Jan '16

30 Jan '16

Hi all, I make ECL compile with Win64 cl compiler, and so far it does not work bad. I want to run the unit test, and I was able to do it manually with some failure but I'm not 100% sure that I run those in the right way. It there some instruction that I can follow or can you tell me wich is the proper way to run those unit test. p.S. The buil system on windows need some makeup (on windows) and I was was wondering that instead of using nmake I can fixup autoconf to work on msys2 on windows platform with native cl compiler. Cheers f.

2 1

Re: [Ecls-list] threading failures
by Daniel Kochmański 22 Jan '16

22 Jan '16

Hello, that's probably my fault, sorry. I've migrated bugs manually and probably missed this one (I remember this bug! but can't find anywhere). I'm adding it to regression tests in repository, thanks! Yes, old reports are unfortunately lost. As a sienote, please use ecl-devel(a)common-lisp.net mailing list – I'm closing the old one today. You can subscribe here https://mailman.common-lisp.net/listinfo/ecl-devel . All archives before 2015-08-10 are imported to the new one and gmane stream is redirected (if you use it). Regards, Daniel James M. Lawrence writes: > Hello, the threading bugs I reported a while ago appear to have not > survived the migration from sourceforge, and the old pages are now > 404'd. There were a number of test cases, including > > (defun test (message-count worker-count) > (let ((to-workers (mp:make-semaphore)) > (from-workers (mp:make-semaphore))) > (loop repeat worker-count > do (mp:process-run-function > "test" > (lambda () > (loop > (mp:wait-on-semaphore to-workers) > (mp:signal-semaphore from-workers))))) > (loop > (loop repeat message-count > do (mp:signal-semaphore to-workers)) > (loop repeat message-count > do (mp:wait-on-semaphore from-workers)) > (assert (zerop (mp:semaphore-count to-workers))) > (assert (zerop (mp:semaphore-count from-workers))) > (format t ".") > (finish-output)))) > > (defun run () > (test 10000 64)) > > RUN will eventually hang on all versions of ECL I've tried, including > the latest. Another test case was a variant of the above using a > homemade semaphore. I can rewrite that and other test cases, but > before doing so I'd like to know whether the old reports are really > lost or have survived in some form. > > Best, > lmj > > ------------------------------------------------------------------------------ > _______________________________________________ > Ecls-list mailing list > Ecls-list(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ecls-list -- Daniel Kochmański | Poznań, Poland ;; aka jackdaniel "Be the change that you wish to see in the world." - Mahatma Gandhi

3 11

[CfP] 9th European Lisp Symposium, May 9-10, Krakow, Poland
by Didier Verna 21 Jan '16

21 Jan '16

ELS'16 - 9th European Lisp Symposium Department of Computer Science AGH University of Science and Technology Kraków, Poland May 9-10, 2016 In cooperation with: ACM SIGPLAN Sponsored by EPITA, Franz Inc., LispWorks Ltd. and Dept. of Computer Science AGH UST http://www.european-lisp-symposium.org/ Recent news: - Submission deadline in less than a month! - 3nd invited speaker announced: Stephan Karpinski on Julia: to Lisp or Not to Lisp? 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 9th 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. Important dates: - 19 Feb 2016 Submission deadline - 25 Mar 2016 Notification of acceptance - 15 Apr 2016 Early registration deadline - 22 Apr 2016 Final papers due - 9-10 May 2016 Symposium Programme chair: Irène Durand, LaBRI, University of Bordeaux, France Local chair: Michał Psota, Emergent Network Defense, Kraków, Poland Programme committee: Antonio Leitao — INESC-ID / Instituto Superior Técnico, Universidade de Lisboa, Portugal Charlotte Heerzel — IMEC, Leuven, Belgium Christian Queinnec — University Pierre et Marie Curie, Paris 6, France Christophe Rhodes — Goldsmiths, University of London, United Kingdom Didier Verna — EPITA Research and Development Laboratory, France Erick Gallesio — University of Nice-Sophia Antipolis, France François-René Rideau, Google, USA Giuseppe Attardi — University of Pisa, Italy Henry Lieberman — MIT, USA Kent Pitman, HyperMeta Inc., USA Leonie Dreschler-Fischer — University of Hamburg, Germany Pascal Costanza — Intel Corporation, Belgium Robert Strandh — University of Bordeaux, France Search Keywords: #els2016, ELS 2016, ELS '16, European Lisp Symposium 2016, European Lisp Symposium '16, 9th ELS, 9th European Lisp Symposium, European Lisp Conference 2016, European Lisp Conference '16 -- @-quartet live: Sunset/Sunside, Paris, Jan 26 2016 ! Book now: http://www.sunset-sunside.com/2016/1/artiste/2101/3453/ Lisp, Jazz, Aïkido: http://www.didierverna.info

1 0

cl-redis problems
by Diogo Franco 11 Jan '16

11 Jan '16

Hi, I've been using cl-redis with ecl without problems, but recently i have some trouble when installing on new systems. rutil is a dependency installed by quicklisp when doing quickload on cl-redis, and i've been getting: "There is no method on the generic function PRINT-OBJECT that agrees on qualifiers NIL and specializers (HASH-TABLE T)" This is the ecl that's installed via apt-get, ecl-13.5.1. I did notice that sbcl finds the method correctly when doing "(find-method #'print-object nil '(hash-table t))", while ecl also gives the error above. Any idea on how to further investigate this? Thanks in advance!

3 3

How to compile executable with external dependencies
by Alexander Artemenko 05 Jan '16

05 Jan '16

Hi! Is there a way to compile a lisp programm which uses something like Drakma? Or ECL is only able to compile separate lisp files one by one? -- Alexander Artemenko (a.k.a. Svetlyak 40wt) Blog: http://dev.svetlyak.ru Photos: http://svetlyak.ru Jabber: svetlyak.40wt(a)gmail.com

2 1

Displaying lisp errors while running with save_eval
by Diogo Franco 08 Dec '15

08 Dec '15

Hi all, Uncaught error conditions in lisp code don't display in *standard-output* for me, when ecl is running embedded in c (i presume the reason is that i'm calling the lisp functions using save_eval()). My workflow on the shell while developing is then to do ctrl-c which drops me to the REPL, and to manually execute the functions, which will print the error. I'm no expert on the inner workings of ecl, so forgive me if this is a dumb question, but is there some way to get the errors in *standard-output* even when using save_eval()? Thanks in advance, Diogo Franco

2 2

Re: Inspecting intermediate C files
by Daniel Kochmański 25 Nov '15

25 Nov '15

Hi, I'm not sure if I miss something, but this mail seems to be sent to the ecl-devel-owner(a)common-lisp.net . Correct ML address is ecl-devel(a)common-lisp.net . I'm fast forwarding the mail there. Brian Beckman writes: > Hello -- > > I am experimenting with ECL for actual embedded applications > (in the sense of "embedded systems," i.e., small computers running > disconnected controller software. > > The hardware team insists on inspecting the generated C code from > the ECL compiler. I found, in the ECL manual, directions for > producing .o files, .a files, .fasl files, and standalone executables. > I also found prose that says that it is possible to emit the > actual .c and .h files. However, I can't find instructions on how > to emit the actual .c and .h files. Generated code is readable, but it's a generated code after all. It's not pretty. > > I can (compile-file "hello.lisp" :system-p t), but that produces > only a .o file. I need to see the .c and .h files. My hardware > team won't permit ECL-generated code until they can visually read > and inspect the generated .c and .h files. To prevent ECL from deleting these intermediate files you need to set special variable c::*delete-files* to nil. (setf c::*delete-files* nil) Intermediate files are *.c, *.h and *.data . The last one contains some untranslatable expressions (rare occasion – if you work with infinities for instance) and debugging/reflection information (like the path to the source file). This problem has been tacled by Earl Ducaine here: https://github.com/earl-ducaine/stupid-ecl-tricks-1 . > > Can you help me figure out how to generate them? I can't find > the instructions in the manual. I am starting to read the source > code, but perhaps you can give me correct pointers into the manual > or some other kind of instructions. I'm now in-process of revising manual and rewriting it into texi sources. I'll keep in mind to document this. It would be great if you could file an issue on gitlab.com/embeddable-common-lisp/ecl/issues (with the label "documentation"). Thanks! > > Thanks! Regards, Daniel -- Daniel Kochmański | Poznań, Poland ;; aka jackdaniel "Be the change that you wish to see in the world." - Mahatma Gandhi

2 1

iolib and close
by Alessandro Serra 25 Nov '15

25 Nov '15

Dear all, compiling "iolib-tests" I received the following error: #<IPv4 datagram socket, closed 00000000050f3660> is not of type STREAM. [Condition of type TYPE-ERROR] I have seen that in "clos/streams.lsp" the following method is defined: (defmethod close ((stream t) &key abort) (declare (ignore abort)) (bug-or-error stream 'close)) Removing the method above with: (remove-method #'gray:close (find-method #'gray:close '() '(t))) I was able to compile iolib-tests and run the tests. Did 71 checks. Pass: 59 (83%) Skip: 0 ( 0%) Fail: 12 (16%) Regards, Alessandro

2 1