armedbear-devel

armedbear-devel@common-lisp.net

1 participants
1200 discussions

[Armedbear-devel] abcl-asdf: merged changes from Cyrus
by Mark Evenson 06 Mar '15

06 Mar '15

Spam detection software, running on the system "mailcrunch1.panix.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see support(a)panix.com for details. Content preview: [Cyrusâs recent patches for ABCL-ASDF to use alternate Maven repositories and other fixes][1] have been merged [into the ABCL trunk][2,3,4,5]. [I made the following deviation from the patches][6]: The codes seems to intend to record, buts fails to actually set, the repository an artifact is download from as part of the path. I changed the ineffective code as a comment, mainly as the MVN path is intended to follow the [MVN URI scheme][7] for which the repository definitely doesnât belong at the end but rather at the beginning. [...] Content analysis details: (5.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 2.4 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net [Blocked - see <http://www.spamcop.net/bl.shtml?109.126.64.2>] 3.6 RCVD_IN_SBL_CSS RBL: Received via a relay in Spamhaus SBL-CSS [109.126.64.2 listed in pgwm4qf5v2mbif3ei5nmvnmsve.zen.dq.spamhaus.net] 0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail domains are different -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature

1 0

[Armedbear-devel] asdf doesn't load dependencies in abcl
by Pascal J. Bourguignon 04 Mar '15

04 Mar '15

When using abcl, asdf doesn't load some dependent packages. In this case, I have asd file com.informatimago.tools.asd -------------------------------------------------------------------------------- (asdf:defsystem :com.informatimago.tools ;; system attributes: :description "This system gathers Informatimago Common Lisp tools." :author "Pascal J. Bourguignon <pjb(a)informatimago.com>" :maintainer "Pascal J. Bourguignon <pjb(a)informatimago.com>" :licence "AGPL3" ;; component attributes: :name "Informatimago Common Lisp Tools Agregate" :version "1.0.2" :properties ((#:author-email . "pjb(a)informatimago.com") (#:date . "Spring 2014") ((#:albert #:output-dir) . "/tmp/documentation/com.informatimago.tools/") ((#:albert #:formats) . ("docbook")) ((#:albert #:docbook #:template) . "book") ((#:albert #:docbook #:bgcolor) . "white") ((#:albert #:docbook #:textcolor) . "black")) #+asdf-unicode :encoding #+asdf-unicode :utf-8 :depends-on ("com.informatimago.tools.check-asdf" "com.informatimago.tools.make-depends" "com.informatimago.tools.manifest" "com.informatimago.tools.pathname" "com.informatimago.tools.source" "com.informatimago.tools.symbol" "com.informatimago.tools.quicklisp") :components ((:file "tools"))) -------------------------------------------------------------------------------- which should load com.informatimago.tools.pathname.asd -------------------------------------------------------------------------------- (asdf:defsystem :com.informatimago.tools.pathname :name "com.informatimago.tools.pathname" :description "Pathname tools." :author "Pascal J. Bourguignon" :version "1.0.0" :license "GPL3" :depends-on () :components ((:file "pathname"))) -------------------------------------------------------------------------------- and pathname.lisp defines a package named "COM.INFORMATIMAGO.TOOLS.PATHNAME": -------------------------------------------------------------------------------- (defpackage "COM.INFORMATIMAGO.TOOLS.PATHNAME" (:use "COMMON-LISP") (:shadow "MAKE-PATHNAME" "USER-HOMEDIR-PATHNAME" "TRANSLATE-LOGICAL-PATHNAME") (:export "MAKE-PATHNAME" "USER-HOMEDIR-PATHNAME" "TRANSLATE-LOGICAL-PATHNAME") (:documentation "Pathname tools.")) ;; etc -------------------------------------------------------------------------------- Unfortunately, it seems that asdf (version "3.1.0.103") fails to load this dependencies: [pjb@kuiper :10.0 lisp]$ abcl Armed Bear Common Lisp 1.3.1 Java 1.7.0_75 Oracle Corporation OpenJDK 64-Bit Server VM Low-level initialization completed in 1.136 seconds. Startup completed in 6.589 seconds. ;; -*- mode:lisp -*- (:OUTPUT-TRANSLATIONS :IGNORE-INVALID-ENTRIES (T (:HOME ".cache" "common-lisp" :HOSTNAME :IMPLEMENTATION)) (T (:HOME ".cache" "common-lisp" :IMPLEMENTATION)) :INHERIT-CONFIGURATION) To load "com.informatimago.common-lisp": Load 1 ASDF system: com.informatimago.common-lisp ; Loading "com.informatimago.common-lisp" [package com.informatimago.common-lisp.lisp-sexp.source-form]. .................................................. [package com.informatimago.common-lisp.lisp-reader.reader]. .................................................. [package com.informatimago.common-lisp.lisp-reader.package]. .................................................. [package com.informatimago.common-lisp.lisp-text.source-text]. [package com.informatimago.common-lisp.cesarum.simple-test]. [package com.informatimago.common-lisp.cesarum.array] [package com.informatimago.common-lisp.cesarum.sequence]. [package com.informatimago.common-lisp.cesarum.list]. .................................................. [package com.informatimago.common-lisp.cesarum.utility]. .................................................. [package com.informatimago.common-lisp.cesarum.ecma048]. [package com.informatimago.common-lisp.cesarum.string]. .................................................. [package com.informatimago.common-lisp.cesarum.package]. [package com.informatimago.common-lisp.cesarum.set]. [package com.informatimago.common-lisp.cesarum.index-set]. .................................................. [package com.informatimago.common-lisp.cesarum.bset]. .................................................. [package com.informatimago.common-lisp.cesarum.brelation]. .................................................. [package com.informatimago.common-lisp.cesarum.dictionary]. [package com.informatimago.common-lisp.cesarum.dll] [package com.informatimago.common-lisp.cesarum.graph]. .................................................. [package com.informatimago.common-lisp.cesarum.llrbtree]. .................................................. [package com.informatimago.common-lisp.cesarum.queue] [package com.informatimago.common-lisp.cesarum.message-queue] [package com.informatimago.common-lisp.cesarum.ascii]. .................................................. [package com.informatimago.common-lisp.cesarum.character]. [package com.informatimago.common-lisp.cesarum.character-sets] [package com.informatimago.common-lisp.cesarum.iso3166] [package com.informatimago.common-lisp.cesarum.iso4217]. [package com.informatimago.common-lisp.cesarum.iso639a] [package com.informatimago.common-lisp.cesarum.pmatch] [package com.informatimago.common-lisp.cesarum.combination]. [package com.informatimago.common-lisp.cesarum.constraints]. [package com.informatimago.common-lisp.cesarum.raiden] [package com.informatimago.common-lisp.cesarum.dfa]. [package com.informatimago.common-lisp.cesarum.tea] [package com.informatimago.common-lisp.cesarum.circular] [package com.informatimago.common-lisp.cesarum.histogram]. [package com.informatimago.common-lisp.cesarum.a-star] [package com.informatimago.common-lisp.cesarum.activity]. .................................................. [package com.informatimago.common-lisp.cesarum.date.utility] [package com.informatimago.common-lisp.julian-calendar] [package com.informatimago.common-lisp.gregorian-calendar] [package com.informatimago.common-lisp.cesarum.date]. .................................................. [package com.informatimago.common-lisp.cesarum.version]. [package com.informatimago.common-lisp.cesarum.stream] [package com.informatimago.common-lisp.cesarum.file]. [package com.informatimago.common-lisp.cesarum.peek-stream]. [package com.informatimago.common-lisp.cesarum.cache]. .................................................. [package com.informatimago.common-lisp.cesarum.float-binio] [package com.informatimago.common-lisp.picture.picture]. .................................................. [package com.informatimago.common-lisp.picture.cons-to-ascii] [package com.informatimago.common-lisp.picture.tree-to-ascii]. [package com.informatimago.common-lisp.arithmetic.primes] [package com.informatimago.common-lisp.arithmetic.p127n2]. [package com.informatimago.common-lisp.data-encoding.data-encoding]. .................................................. [package com.informatimago.common-lisp.data-encoding.bencode]. [package com.informatimago.common-lisp.data-encoding.hexadecimal]. [package com.informatimago.common-lisp.data-encoding.ecp]. [package com.informatimago.common-lisp.heap.memory]. [package com.informatimago.common-lisp.heap.heap]. .................................................. [package com.informatimago.common-lisp.html-generator.html-entities]. .................................................. [package com.informatimago.common-lisp.html-generator.html]. .................................................. [package com.informatimago.common-lisp.html-parser.parse-html]. .................................................. [package com.informatimago.common-lisp.http.hquery] [package com.informatimago.common-lisp.http.htrans]. .................................................. [package com.informatimago.common-lisp.bank.iban]. [package com.informatimago.common-lisp.bank.rib].. [package com.informatimago.common-lisp.csv.csv]... [package com.informatimago.common-lisp.diagram.tree-to-diagram] [package com.informatimago.common-lisp.regexp.regexp-emacs]. .................................................. [package com.informatimago.common-lisp.regexp.regexp-posix] [package com.informatimago.common-lisp.regexp.regexp-posix.keyword]. .. ; in (DEFUN RMATCH-B-ANCHOR ...) ; Caught STYLE-WARNING: ; The variable #:G193370 is defined but never used. ; in (DEFUN RMATCH-E-ANCHOR ...) ; Caught STYLE-WARNING: ; The variable #:G193396 is defined but never used. ; in (DEFUN RMATCH-L-ANCHOR ...) ; Caught STYLE-WARNING: ; The variable #:G193423 is defined but never used. ; in (DEFUN RMATCH-R-ANCHOR ...) ; Caught STYLE-WARNING: ; The variable #:G193457 is defined but never used. ; in (DEFUN RMATCH-ANY ...) ; Caught STYLE-WARNING: ; The variable #:G193492 is defined but never used. .. ; Caught COMPILE-WARNED-WARNING: ; Lisp compilation had style-warnings while compiling #<ASDF/LISP-ACTION:CL-SOURCE-FILE "com.informatimago.common-lisp.regexp" "regexp-posix"> .............................................. [package com.informatimago.common-lisp.ed.ed]..... [package com.informatimago.common-lisp.graphviz.graph-dot] [package com.informatimago.common-lisp.invoice.invoice]. .................................................. [package com.informatimago.common-lisp.interactive.browser]. [package com.informatimago.common-lisp.interactive.interactive]. .................................................. [package com.informatimago.common-lisp.parser.scanner]. [package com.informatimago.common-lisp.parser.parser]. [package com.informatimago.common-lisp.rfc2822.rfc2822] [package com.informatimago.common-lisp.rfc3548.rfc3548]. [package com.informatimago.common-lisp.unix.aliases]. [package com.informatimago.common-lisp.unix.group] [package com.informatimago.common-lisp.unix.passwd]. [package com.informatimago.common-lisp.unix.option]. ; Compilation unit finished ; Caught 1 WARNING condition ; Caught 5 STYLE-WARNING conditions To load "com.informatimago.common-lisp.lisp.stepper": Load 1 ASDF system: com.informatimago.common-lisp.lisp.stepper ; Loading "com.informatimago.common-lisp.lisp.stepper" [package com.informatimago.common-lisp.lisp.stepper.internal]. .................................................. [package com.informatimago.common-lisp.lisp.stepper]. . To load "com.informatimago.clmisc": Load 1 ASDF system: com.informatimago.clmisc ; Loading "com.informatimago.clmisc" [package com.informatimago.clmisc.resource-utilization] To load "com.informatimago.tools": Load 1 ASDF system: com.informatimago.tools ; Loading "com.informatimago.tools" To load "com.informatimago.clext": Load 1 ASDF system: com.informatimago.clext ; Loading "com.informatimago.clext" [package closer-mop].............................. [package closer-common-lisp]...................... [package closer-common-lisp-user]................. [package com.informatimago.clext.association]..... [package com.informatimago.clext.character-sets]. To load "alexandria": Load 1 ASDF system: alexandria ; Loading "alexandria" [package alexandria.0.dev].... Error loading /home/pjb/rc/common.lisp at line 262 (offset 9763) #<THREAD "interpreter" {7C9CC8FE}>: Debugger invoked on condition of type READER-ERROR The package "COM.INFORMATIMAGO.TOOLS.PATHNAME" can't be found. [1] PJB(1): (asdf/upgrade:asdf-version) "3.1.0.103" [1] PJB(2): For reference, the same script run by ccl (with asdf version "3.1.3"): [pjb@kuiper :10.0 lisp]$ ccl ;; -*- mode:lisp -*- (:OUTPUT-TRANSLATIONS :IGNORE-INVALID-ENTRIES (T (:HOME ".cache" "common-lisp" :HOSTNAME :IMPLEMENTATION)) (T (:HOME ".cache" "common-lisp" :IMPLEMENTATION)) :INHERIT-CONFIGURATION) To load "com.informatimago.common-lisp": Load 1 ASDF system: com.informatimago.common-lisp ; Loading "com.informatimago.common-lisp" [package com.informatimago.common-lisp.lisp-sexp.source-form]. .................................................. [package com.informatimago.common-lisp.lisp-reader.reader]. .................................................. [package com.informatimago.common-lisp.lisp-reader.package]. .................................................. [package com.informatimago.common-lisp.lisp-text.source-text]. [package com.informatimago.common-lisp.cesarum.simple-test]. [package com.informatimago.common-lisp.cesarum.array] [package com.informatimago.common-lisp.cesarum.sequence]. [package com.informatimago.common-lisp.cesarum.list]. .................................................. [package com.informatimago.common-lisp.cesarum.utility]. .................................................. [package com.informatimago.common-lisp.cesarum.ecma048] [package com.informatimago.common-lisp.cesarum.string]. .................................................. [package com.informatimago.common-lisp.cesarum.package]. [package com.informatimago.common-lisp.cesarum.set]. [package com.informatimago.common-lisp.cesarum.index-set]. [package com.informatimago.common-lisp.cesarum.bset]. .................................................. [package com.informatimago.common-lisp.cesarum.brelation]. .................................................. [package com.informatimago.common-lisp.cesarum.dictionary]. [package com.informatimago.common-lisp.cesarum.dll]. [package com.informatimago.common-lisp.cesarum.graph]. [package com.informatimago.common-lisp.cesarum.llrbtree]. .................................................. [package com.informatimago.common-lisp.cesarum.queue] [package com.informatimago.common-lisp.cesarum.message-queue]. [package com.informatimago.common-lisp.cesarum.ascii]. [package com.informatimago.common-lisp.cesarum.character] [package com.informatimago.common-lisp.cesarum.character-sets]. [package com.informatimago.common-lisp.cesarum.iso3166] [package com.informatimago.common-lisp.cesarum.iso4217] [package com.informatimago.common-lisp.cesarum.iso639a]. [package com.informatimago.common-lisp.cesarum.pmatch] [package com.informatimago.common-lisp.cesarum.combination]. [package com.informatimago.common-lisp.cesarum.constraints]. [package com.informatimago.common-lisp.cesarum.raiden] [package com.informatimago.common-lisp.cesarum.dfa]. .................................................. [package com.informatimago.common-lisp.cesarum.tea] [package com.informatimago.common-lisp.cesarum.circular] [package com.informatimago.common-lisp.cesarum.histogram]. [package com.informatimago.common-lisp.cesarum.a-star] [package com.informatimago.common-lisp.cesarum.activity]. .................................................. [package com.informatimago.common-lisp.cesarum.date.utility] [package com.informatimago.common-lisp.julian-calendar] [package com.informatimago.common-lisp.gregorian-calendar] [package com.informatimago.common-lisp.cesarum.date]. .................................................. [package com.informatimago.common-lisp.cesarum.version] [package com.informatimago.common-lisp.cesarum.stream] [package com.informatimago.common-lisp.cesarum.file]. [package com.informatimago.common-lisp.cesarum.peek-stream]. [package com.informatimago.common-lisp.cesarum.cache]. [package com.informatimago.common-lisp.cesarum.float-binio]. [package com.informatimago.common-lisp.picture.picture]. [package com.informatimago.common-lisp.picture.cons-to-ascii] [package com.informatimago.common-lisp.picture.tree-to-ascii]. [package com.informatimago.common-lisp.arithmetic.primes] [package com.informatimago.common-lisp.arithmetic.p127n2]. [package com.informatimago.common-lisp.data-encoding.data-encoding]. .................................................. [package com.informatimago.common-lisp.data-encoding.bencode] [package com.informatimago.common-lisp.data-encoding.hexadecimal]. [package com.informatimago.common-lisp.data-encoding.ecp]. .................................................. [package com.informatimago.common-lisp.heap.memory] [package com.informatimago.common-lisp.heap.heap]. .................................................. [package com.informatimago.common-lisp.html-generator.html-entities]. .................................................. [package com.informatimago.common-lisp.html-generator.html]. .................................................. [package com.informatimago.common-lisp.html-parser.parse-html]. .................................................. [package com.informatimago.common-lisp.http.hquery] [package com.informatimago.common-lisp.http.htrans]. [package com.informatimago.common-lisp.bank.iban]. [package com.informatimago.common-lisp.bank.rib].. [package com.informatimago.common-lisp.csv.csv]... [package com.informatimago.common-lisp.diagram.tree-to-diagram] [package com.informatimago.common-lisp.regexp.regexp-emacs]. .................................................. [package com.informatimago.common-lisp.regexp.regexp-posix] [package com.informatimago.common-lisp.regexp.regexp-posix.keyword]. .................................................. [package com.informatimago.common-lisp.ed.ed]..... [package com.informatimago.common-lisp.graphviz.graph-dot] [package com.informatimago.common-lisp.invoice.invoice]. .................................................. [package com.informatimago.common-lisp.interactive.browser]. [package com.informatimago.common-lisp.interactive.interactive]. [package com.informatimago.common-lisp.parser.scanner] [package com.informatimago.common-lisp.parser.parser] [package com.informatimago.common-lisp.rfc2822.rfc2822]. [package com.informatimago.common-lisp.rfc3548.rfc3548]. .................................................. [package com.informatimago.common-lisp.unix.aliases]. [package com.informatimago.common-lisp.unix.group] [package com.informatimago.common-lisp.unix.passwd] [package com.informatimago.common-lisp.unix.option]. . To load "com.informatimago.common-lisp.lisp.stepper": Load 1 ASDF system: com.informatimago.common-lisp.lisp.stepper ; Loading "com.informatimago.common-lisp.lisp.stepper" [package com.informatimago.common-lisp.lisp.stepper.internal] [package com.informatimago.common-lisp.lisp.stepper]. . To load "com.informatimago.clmisc": Load 1 ASDF system: com.informatimago.clmisc ; Loading "com.informatimago.clmisc" [package com.informatimago.clmisc.resource-utilization] To load "com.informatimago.tools": Load 1 ASDF system: com.informatimago.tools ; Loading "com.informatimago.tools" [package closer-mop].............................. [package closer-common-lisp]...................... [package closer-common-lisp-user]................. [package com.informatimago.clext.association]..... [package com.informatimago.clext.character-sets].. [package com.informatimago.clext.closer-weak]..... [package com.informatimago.clext.closer-weak-user]. .................................................. [package com.informatimago.tools.dependency-cycles]. [package com.informatimago.common-lisp.script].... [package com.informatimago.tools.asdf-file]....... [package com.informatimago.tools.check-asdf]...... [package com.informatimago.common-lisp.tools.make-depends]. .................................................. [package asdf].................................... [package split-sequence].......................... [package com.informatimago.tools.manifest]........ [package com.informatimago.tools.pathname]........ [package com.informatimago.read-sources].......... [package com.informatimago.tools.symbol].......... [package com.informatimago.tools.quicklisp]....... [package com.informatimago.tools.asdf] To load "alexandria": Load 1 ASDF system: alexandria ; Loading "alexandria" [package alexandria.0.dev]........ (OPTIMIZE (SAFETY 3) (DEBUG 3) (SPEED 0) (SPACE 0) (COMPILATION-SPEED 1)) Welcome to Clozure Common Lisp Version 1.10-r16196 (LinuxX8664)! CCL is developed and maintained by Clozure Associates. For more information about CCL visit http://ccl.clozure.com. To enquire about Clozure's Common Lisp consulting services e-mail info(a)clozure.com or visit http://www.clozure.com. ? (asdf/upgrade:asdf-version) "3.1.3" ? (quit) -- __Pascal Bourguignon__ http://www.informatimago.com/ “The factory of the future will have only two employees, a man and a dog. The man will be there to feed the dog. The dog will be there to keep the man from touching the equipment.” -- Carl Bass CEO Autodesk _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net https://mailman.common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

2 1

[Armedbear-devel] [Final CfP] ELS 2015 submission deadline extended to March 1st
by Didier Verna 22 Feb '15

22 Feb '15

ELS'15 - 8th European Lisp Symposium Goldsmiths College, London, UK April 20-21, 2015 http://www.european-lisp-symposium.org/ Sponsored by EPITA, Franz Inc. and Lispworks Ltd. Recent news: - *** Submission deadline extended to March 1st *** - Invited speakers announced: Zach Beane, Bodil Stokke, Martin Cracauer - Registration to open early March 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 8th 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. Important dates: - 01 Mar 2015: Submission deadline *** EXTENDED *** - 15 Mar 2015: Notification of acceptance - 29 Mar 2015: Early registration deadline - 05 Apr 2015: Final papers - 20-21 Apr 2015: Symposium Programme chair: Julian Padget, University of Bath, UK Local chair: Christophe Rhodes, Goldsmiths, University of London, UK Programme committee: Sacha Chua — Toronto, Canada Edmund Weitz — University of Applied Scicences, Hamburg, Germany Rainer Joswig — Hamburg, Germany Henry Lieberman — MIT, USA Matthew Flatt — University of Utah, USA Christian Queinnec — University Pierre et Marie Curie, Paris 6, France Giuseppe Attardi — University of Pisa, Italy Marc Feeley — University of Montreal, Canada Stephen Eglen — University of Cambridge, UK Robert Strandh — University of Bordeaux, France Nick Levine — RavenPack, Spain Search Keywords: #els2015, ELS 2015, ELS '15, European Lisp Symposium 2015, European Lisp Symposium '15, 8th ELS, 8th European Lisp Symposium, European Lisp Conference 2015, European Lisp Conference '15 -- My new Jazz CD entitled "Roots and Leaves" is out! Check it out: http://didierverna.com/records/roots-and-leaves.php Lisp, Jazz, Aïkido: http://www.didierverna.info _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net https://mailman.common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

1 0

[Armedbear-devel] flet+inline warns and generate bad code.
by Pascal J. Bourguignon 21 Feb '15

21 Feb '15

An inline flet makes the compiler report an error (warning?): (defun f (x) (flet ((hello (x) (logand x #xffffffff))) (declare (inline hello)) (hello (+ (hello 1) (hello x))))) CL-USER(6): (compile-file #P"~/abcl-flet-bug.lisp") ; Compiling /home/pjb/abcl-flet-bug.lisp ... ; (DEFUN F ...) ; (DEFUN G ...) ; Compilation unit finished ; The following functions were used but not defined: ; HELLO ; Wrote /home/pjb/abcl-flet-bug.abcl (0.04 seconds) #P"/home/pjb/abcl-flet-bug.abcl" NIL NIL And the code generated is wrong: CL-USER(12): (load(compile-file #P"~/abcl-flet-bug.lisp")) ; Compiling /home/pjb/abcl-flet-bug.lisp ... ; (DEFUN F ...) ; Compilation unit finished ; The following functions were used but not defined: ; HELLO ; Wrote /home/pjb/abcl-flet-bug.abcl (0.012 seconds) T CL-USER(13): (f 4) #<THREAD "interpreter" {6A4E43EA}>: Debugger invoked on condition of type UNDEFINED-FUNCTION The function HELLO is undefined. Restarts: 0: CONTINUE Try again. 1: USE-VALUE Specify a function to call instead. 2: RETURN-VALUE Return one or more values from the call to HELLO. 3: TOP-LEVEL Return to top level. [1] CL-USER(14): 3 CL-USER(15): Without inline, it works well. CL-USER(15): (load(compile-file #P"~/abcl-flet-bug.lisp")) ; Compiling /home/pjb/abcl-flet-bug.lisp ... ; (DEFUN F ...) ; Wrote /home/pjb/abcl-flet-bug.abcl (0.02 seconds) T CL-USER(16): (f 4) 5 CL-USER(17): CL-USER(11): (COM.INFORMATIMAGO.TOOLS.MANIFEST:PRINT-BUG-REPORT-INFO) LISP-IMPLEMENTATION-TYPE "Armed Bear Common Lisp" LISP-IMPLEMENTATION-VERSION "1.3.1" SOFTWARE-TYPE "Linux" SOFTWARE-VERSION "3.2.0-4-amd64" MACHINE-INSTANCE "kuiper" MACHINE-TYPE "X86-64" MACHINE-VERSION "Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz" distribution (:LINUX :DEBIAN "7.8") uname -a NIL *FEATURES* (:COM.INFORMATIMAGO.PJB :SPLIT-SEQUENCE :CLOSER-MOP :COM.INFORMATIMAGO.COMMON-LISP.LISP.CL-STEPPER :NEWLINE-IS-LINEFEED :HAS-ASCII-CODE :HAS-VT :HAS-BELL :HAS-ESCAPE :HAS-LINEFEED :HAS-RETURN :HAS-BACKSPACE :HAS-TAB :HAS-PAGE :HAS-RUBOUT :QUICKLISP :ASDF-PACKAGE-SYSTEM :ASDF3.1 :ASDF3 :ASDF2 :ASDF :OS-UNIX :ASDF-UNICODE :ABCL-BUNDLE-OP-SUPPORTED :X86-64 :JAVA-1.7 :UNIX :LINUX :ARMEDBEAR :ABCL :COMMON-LISP :ANSI-CL :CDR6 :MOP :PACKAGE-LOCAL-NICKNAMES) /proc/cpuinfo ------------- processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz stepping : 5 microcode : 0x11 cpu MHz : 3073.461 cache size : 8192 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc up arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm dtherm tpr_shadow vnmi flexpriority ept vpid bogomips : 6146.92 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: CL-USER(12): -- __Pascal Bourguignon__ http://www.informatimago.com/ “The factory of the future will have only two employees, a man and a dog. The man will be there to feed the dog. The dog will be there to keep the man from touching the equipment.” -- Carl Bass CEO Autodesk _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net https://mailman.common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

1 0

[Armedbear-devel] Question about pipes
by Sistemas 27 Sep '14

27 Sep '14

Hi: I'm trying to start some processes and connect them using pipes with ABCL (like Unix shell pipes). I've reviewed the documentation but I haven't found anything. Are I missing something? If not, are there any plans of adding input, output and error parameters for run-program (like SBCL, CCL, etc.)? Greets and thanks in advance. Rafael J. Alcántara Pérez. -- +---------- | Departamento de Sistemas <sistemas(a)dedaloingenieros.com> | Teléfono fijo: 952 602 959 | Fax: 952 602 959 | Dirección: C/ Afligidos 2, 3º Derecha, 29015 Málaga | Dédalo Ingenieros, S.L.: http://www.dedaloingenieros.com/ | PGP: http://pgp.rediris.es:11371/pks/lookup?op=index&search=0x1899F325 +--------------------- _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

5 7

[Armedbear-devel] Comments on Cyrus's proposal for JSS static calls
by Mark Evenson 27 Sep '14

27 Sep '14

Erik asked me to comment on [Cyrus’s proposed patch][1] to extend JSS’s SHARPSIGN-DOUBLE-QUOTE use in static method calls to accept a string as well as a symbol to designate the object. Unfortunately, changing JSS in the manner means that one can no longer use SHARPSIGN-DOUBE-QUOTE on object descended from java.lang.String, for the reasons described in the [JSS README][2]: […] Static calls are possible as well with the #" macro, but the first argument MUST BE A SYMBOL to distinguish (#"getProperties" "java.lang.System") from (#"getProperties" 'java.lang.System) The first attempts to call a method on the java.lang.String object with the contents "java.lang.System", which results in an error, while the second invokes the static java.lang.System.getProperties() method. […] Other than perhaps for aesthetic reasons, is there some functionality that using strings enables here? To argue about preserving character case in strings as opposed to the case folding implicit in symbols doesn’t seem to be applicable, because JSS currently ignores case when searching for matching JVM symbols. In 2006, when I first understood the ignoring case bit of JSS, I was a bit worried that there would be cases where this resulted in ambiguity and errors, but in the ensuing years I have yet to run into a single problem with this design decision. Therefore, I am not currently persuaded that introducing an asymmetry to SHARPSIGN-DOUBLE-QUOTE (“It works on any java Object except those which descend from java.lang.String; for those instances you have to use the JFI”) to use strings as well as symbols to specify static methods is worth it. But please argue back if you disagree… [1]: https://github.com/slyrus/abcl/commit/9ec0fb26c7b7e9470349b1c4bd9be6fa4b053… [2]: http://abcl.org/trac/browser/trunk/abcl/contrib/jss/README.markdown#L55 -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now." _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

3 2

[Armedbear-devel] Bug: compile function doesn't work
by Mariano Montone 27 Sep '14

27 Sep '14

Hello, This function is not working in the latest ABCL version: http://clhs.lisp.se/Body/f_cmp.htm This is what I get when I try to evaluate the example in CLHS: (defun foo () "bar") => FOO (compile 'foo) Wrong number of arguments for #<FUNCTION {5236A94B}>. [Condition of type PROGRAM-ERROR] Restarts: 0: [RETRY] Retry SLIME REPL evaluation request. 1: [*ABORT] Return to SLIME's top level. 2: [ABORT] Abort thread. Backtrace: 0: (#<FUNCTION {752CC03}> #<PROGRAM-ERROR {600776A0}> #<FUNCTION {752CC03}>) 1: (APPLY #<FUNCTION {752CC03}> (#<PROGRAM-ERROR {600776A0}> #<FUNCTION {752CC03}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<PROGRAM-ERROR {600776A0}> #<FUNCTION {752CC03}>) 3: (INVOKE-DEBUGGER #<PROGRAM-ERROR {600776A0}>) 4: org.armedbear.lisp.Lisp.error(Lisp.java:382) 5: org.armedbear.lisp.CompiledClosure.notImplemented(CompiledClosure.java:81) 6: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:212) 7: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:121) 8: org.armedbear.lisp.FuncallableStandardObject.execute(FuncallableStandardObject.java:117) 9: org.armedbear.lisp.Symbol.execute(Symbol.java:826) 10: org.armedbear.lisp.compiler_pass2_387.execute(compiler-pass2.lisp:7495) 11: org.armedbear.lisp.compiler_pass2_370.execute(compiler-pass2.lisp:7450) 12: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:98) 13: org.armedbear.lisp.Symbol.execute(Symbol.java:803) 14: org.armedbear.lisp.compiler_pass2_386.execute(compiler-pass2.lisp:7495) 15: org.armedbear.lisp.Symbol.execute(Symbol.java:838) 16: org.armedbear.lisp.compiler_pass2_388.execute(compiler-pass2.lisp:7519) 17: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:109) 18: org.armedbear.lisp.Symbol.execute(Symbol.java:814) 19: org.armedbear.lisp.compiler_pass2_392.execute(compiler-pass2.lisp:7589) 20: org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:98) 21: org.armedbear.lisp.LispThread.execute(LispThread.java:814) 22: org.armedbear.lisp.Lisp.evalCall(Lisp.java:575) 23: org.armedbear.lisp.Lisp.eval(Lisp.java:540) 24: org.armedbear.lisp.Primitives$pf__eval.execute(Primitives.java:345) 25: (COMPILE FOO) I'm not using this directly, but some libraries like closer-mop, need compile to work. Fails here: CL-USER> (lisp-implementation-type) "Armed Bear Common Lisp" CL-USER> (lisp-implementation-version) "1.4.0-dev-svn-14713" "OpenJDK_64-Bit_Server_VM-Oracle_Corporation-1.7.0_55-b14" "amd64-Linux-3.5.0-17-generic" It seems to work in some cases on ABCL 1.3.1, though. CL-USER> (compile 'foo) FOO NIL NIL But something like this signals an error: CL-USER> (compile nil '(lambda (x) x)) ; Evaluation aborted on #<PROGRAM-ERROR {4C62C417}>. With the same error above. CL-USER> (lisp-implementation-version) "1.3.1" "OpenJDK_64-Bit_Server_VM-Oracle_Corporation-1.7.0_55-b14" "amd64-Linux-3.5.0-17-generic" I couldn't put this on the bugs tracker because I don't have permissions. Cheers, Mariano _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

2 3

Re: [Cffi-devel] Patches to CFFI for ABCL which passes all tests
by Cyrus Harmon 27 Sep '14

27 Sep '14

On Aug 20, 2014, at 2:24 AM, Mark Evenson <evenson(a)panix.com> wrote: > > Even though we are passing all the CFFI tests, > > CL-USER> (drakma:http-request “https://google.com”) > > still times out with an error. Always something further to fix… Yes, I’ve run across this too. The first https call hangs, even if one adds :connection-timeout 120. Could we be improperly initializing something somewhere along the run? After recovering from this error, subsequent calls work. This is probably more of a cl+ssl issue than a cffi (or ABCL) issue, but it definitely seems to be ABCL-specific. Thanks for your work to clean up the CFFI patch set! I look forward to the day when I can run stock CFFI, cl+ss, and ABCL and have all my code working :) Cyrus

3 3

[Armedbear-devel] [CfPart] International Lisp Conference 2014, August 15-17, Montreal
by Didier Verna 19 Aug '14

19 Aug '14

ILC 2014 - International Lisp Conference "Lisp on the Move" August 15-17 2014, Université de Montréal, Montréal, Canada Sponsored by the Association of Lisp Users In cooperation with: ACM SIGPLAN http://ilc2014.iro.umontreal.ca/ Latest News: * Registration is now open. See http://ilc2014.iro.umontreal.ca/registration.php * Invited speakers announced. Christian Queinnec, Ambrose Bonnaire-Sergeant, Stefan Monnier, Marc Battyani. Scope: Lisp is one of the greatest ideas from computer science and a major influence for almost all programming languages and for all sufficiently complex software applications. The International Lisp Conference is a forum for the discussion of Lisp and, in particular, the design, implementation and application of any of the Lisp dialects. We encourage everyone interested in Lisp to participate. This year's focus is directed towards integrated solutions, including mobile computing. The conference also provides slots for lightning talks, to be registered on-site every day. The full programme is available here: http://ilc2014.iro.umontreal.ca/program.php Important Dates: - July 14, 2014: Early registration deadline - August 15, 2014: Conference starts Organizing Committee: General Chair: Marc Feeley (Université de Montréal, Montréal, Canada) Programme Chair: Didier Verna (EPITA Research lab, Paris, France) Local chair: Marc Feeley (Université de Montréal, Montréal, Canada) Programme Committee: Charlotte Herzeel, IMEC, ExaScience Life Lab, Belgium Dave Herman, Mozilla Research, USA Greg Pfeil, Clozure Associates, USA Irène Anne Durand, LaBRI University of Bordeaux, France Jim Newton, Cadence Design Systems, France Kuroda Hisao, Mathematical Systems Inc., Japan Matthew Might, University of Utah, USA Nicolas Neuss, Friedrich Alexander Universitat, Germany Ralf Möller, TUHH, Germany Sam Tobin-Hochstadt, Northeastern University, USA William Byrd, University of Utah, USA Contact: ilc14-organizing-committee at alu.org For more information, see http://ilc2014.iro.umontreal.ca/ -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

1 0

[Armedbear-devel] Motion to delete asdf-install from ABCL's contrib
by Erik Huelsmann 19 Aug '14

19 Aug '14

Hi all, Relaying a motion by slyrus (Cyrus Harmon) from IRC: can we delete asdf-install from ABCL's contrib package? I think we can and should, given that we now have Quicklisp well supported, so hereby I'm relaying. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in. _______________________________________________ Armedbear-devel mailing list Armedbear-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel