March 2010 - cmucl-imp - mailman3.common-lisp.net

Re: [cmucl-imp] PCL::*OPTIMIZE-GF-CALLS-P* bug when GF name is shadowed lexically
by Raymond Toy 25 Apr '10

25 Apr '10

On 2/18/10 8:49 PM, Madhu wrote: > CMUCL does not correctly handle FLETs in DEFMETHOD bodies which use the > same name as that of the generic function. > An example might be: > > ; (setq pcl::*optimize-gf-calls-p* t) > (defmethod foo (bar var) (format t "GENERICFOO ~S, ~S.%" bar var)) > > (defclass fnarr ()()) > > (defmethod foo ((bar fnarr) var) > (flet ((foo (&optional arg) > (foo var (class-of arg)))) ; gf FOO call > (foo bar))) ; local function FOO call > > ;; (incorrect) Error when evaluating > (foo (make-instance 'fnarr) t) > > > Perhaps the immediate symptom can be treated in WALK-METHOD-LAMBDA as > follows? -- Madhu > I'm not familiar with PCL at all, but that looks reasonable. I'll check it in shortly. Ray

2 4

I18n branch merged to trunk
by Raymond Toy 19 Mar '10

19 Mar '10

The i18n branch (intl-branch) has been merged to the trunk. To build this, you need to use boot-2010-02-1.lisp as the bootstrap file with build.sh. You may also want to use the -P option for build.sh to generate/update the po files with any new strings. There's an updated Pig latin (machine) translation that includes translations for all strings in CMUCL. Currently, hemlock, clx, and clm are not translated. It might be nice to support clx, but since that is from an external source, I'd rather not touch it. I've test this briefly on Mac OS X and Linux, and only with the unicode builds. Everything seems to be working. Ray

1 0

Redefining structure accessors (summary)
by Raymond Toy 18 Mar '10

18 Mar '10

Let's see if I can summarize the discussion. Attempts to redefine structure accessors should be a cerror. If you continue, then the structure is undefined (mostly) and the function is created. This seems better than the current behavior of just warning you about it and undefining the structure anyway. (compile accessor new-def) should also be a cerror. (setf (fdefinition accessor) new-def) shouldn't do anything special. The structure printer and inspector should be modified to use %instance-ref so that we can still print and inspect structures even if the accessor has been redefined. How does that sound? Ray

2 7

[2nd CfP] 7th European Lisp Workshop at ECOOP'10, June 21/22
by Didier Verna 17 Mar '10

17 Mar '10

+------------------------------------------------------------+ | 2ND CALL FOR PAPERS | | 7th European Lisp Workshop | | June 21/22, Maribor, Slovenia - co-located with ECOOP 2010 | +------------------------------------------------------------+ News ==== Our invited speaker, Manuel Serrano, will talk about "diffuse programming" and HOP. The abstract of his presentation can be found on the website at: http://european-lisp-workshop.org/upcoming/programme.php Important Dates =============== Submission deadline: April 19, 2010 Notification of acceptance: May 05, 2010 ECOOP early registration deadline: May 10, 2010 7th European Lisp Workshop: June 21 or 22, 2010 (tbdl) Please note that registration must be done with ECOOP itself. For more information visit http://www.european-lisp-workshop.org Contact: Didier Verna, didier(a)lrde.epita.fr Invited Speaker =============== Manuel Serrano (INRIA, France) http://www-sop.inria.fr/members/Manuel.Serrano/ Overview ======== "...Please don't assume Lisp is only useful for Animation and Graphics, AI, Bio-informatics, B2B and E-Commerce, Data Mining, EDA/Semiconductor applications, Expert Systems, Finance, Intelligent Agents, Knowledge Management, Mechanical CAD, Modeling and Simulation, Natural Language, Optimization, Research, Risk Analysis, Scheduling, Telecom, and Web Authoring just because these are the only things they happened to list." -- Kent Pitman Lisp, one of the eldest computer languages still in use today, is gaining momentum again. The structure of Lisp makes it easy to extend the language or even to implement entirely new dialects without starting from scratch, making it the ideal candidate for writing Domain Specific Languages. Common Lisp, with the Common Lisp Object System (CLOS), was the first object-oriented programming language to receive an ANSI standard and remains the most complete and advanced object system of any programming language, while influencing many other object-oriented programming languages that followed. This workshop will address the near-future role of Lisp-based languages in research, industry and education. We solicit contributions that discuss the opportunities Lisp provides to capture and enhance the possibilities in software engineering. We want to promote lively discussion between researchers proposing new approaches and practitioners reporting on their experience with the strengths and limitations of current Lisp technologies. The workshop will have two components: there will be formal talks, and interactive turorial/demo/coding sessions. Papers ====== Formal presentations in the workshop should take between 20 minutes and half an hour; additional time will be given for questions and answers. Suggested topics include (but are not limited to): - Context-, aspect-, domain-oriented and generative programming - Macro-, reflective-, meta- and/or rule-based development approaches - Protocol meta-programming and libraries - New language features and abstractions - Software evolution - Development aids - Persistent systems - Dynamic optimization - Implementation techniques - Hardware Support - Efficiency, distribution and parallel programming - Educational approaches and perspectives - Experience reports and case studies Interactive Tutorial/Demo/Coding Sessions ========================================= Additionally, we invite less formal talks in the form of interactive tutorial/demo/coding sessions. The purpose of these sessions is both to demonstrate and receive feedback on any interesting Lisp system, either stable or under development. Being less formal than technical paper presentations, these sessions are expected to be highly interactive. Submission Guidelines ===================== Potential contributors are encouraged to submit: - a long paper (around 10 pages) presenting scientific and/or empirical results about Lisp-based uses or new approaches for software engineering purposes, - a short essay (5 pages) defending a position about where research, practice or education based on Lisp should be heading in the near future, - a proposal for an interactive tutorial/demo/coding session (1-2 pages) describing the involved library or application, and the subject of the session. Papers (both long and short) should be formatted following the ACM SIGS guidelines and include ACM classification categories and terms (see below). Authors will later be required to sign an ACM copyright form, as the workshop proceedings will be published in the ACM Digital Library. For more information on the submission guidelines and the ACM keywords, see: http://www.acm.org/sigs/publications/proceedings-templates http://www.acm.org/about/class/1998 Submissions should be uploaded to Easy Chair, at the following address: http://www.easychair.org/conferences/?conf=elw2010 Organizers ========== Didier Verna, EPITA Research and Development Laboratory, Paris Charlotte Herzeel, Programming Technology Lab, Vrije Universiteit, Brussel Robert Strandh, LaBRI, University of Bordeaux 1, France Christophe Rhodes, Goldsmiths College, University of London -- Resistance is futile. You will be jazzimilated. Scientific site: http://www.lrde.epita.fr/~didier Music (Jazz) site: http://www.didierverna.com

1 0

Compiled COMPILE forms at load time Bug
by Madhu 16 Mar '10

16 Mar '10

CMUCL's file compiler does not correctly compile "top level" COMPILE forms in the source. Quick sketch: $ echo '(compile nil (lambda (x) x))' > foo.lisp $ lisp -noinit * (compile-file "foo.lisp") * (load *) At FASL Load Time this results in an error, with a `back' stack that looks like: Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: NIL is not of type C::DEBUG-SOURCE 0: (FUNCTION-LAMBDA-EXPRESSION #<Function "COMPILE NIL" {5863BFB1}>) 1: (C::GET-LAMBDA-TO-COMPILE #<Function "COMPILE NIL" {5863BFB1}>) 2: ((FLET #:G0 COMPILE)) 3: (COMPILE NIL #<Function "COMPILE NIL" {5863BFB1}>) 4: (COMPILE 2 NIL #<Function "COMPILE NIL" {5863BFB1}>)[:EXTERNAL] 5: (C::DO-CALL #<Code Object "Top-Level Form" {5863C087}> 4 5 4 ...) 6: (LISP::FOP-FUNCALL-FOR-EFFECT) 7: (LISP::LOAD-GROUP #<Stream for file "/home/madhu/foo.x86f">) 8: (LISP::FASLOAD #<Stream for file "/home/madhu/foo.x86f">) 9: (LISP::INTERNAL-LOAD #P"/home/madhu/foo.x86f" #P"/home/madhu/foo.x86f" :ERROR :BINARY ...) [I think this behaviour has been around for a long time (?), and it is a bug because it prevents you from ensuring compiled functions are stored in DEFVAR forms.] -- Madhu

4 30

Fwd: [Bug 539517] [NEW] DEFINE-CONDITION and constant :DEFAULT-INITARGS
by Nikodemus Siivola 16 Mar '10

16 Mar '10

This gems lives in CMUCL too. :) ---------- Forwarded message ---------- From: Nikodemus Siivola <nikodemus(a)random-state.net> Date: 16 March 2010 14:03 Subject: [Bug 539517] [NEW] DEFINE-CONDITION and constant :DEFAULT-INITARGS To: nikodemus(a)random-state.net Public bug reported: CL-USER> (defconstant +foo+ (lambda () (error "oops"))) +FOO+ CL-USER> (define-condition test () ((xxx :initarg :xxx)) (:default-initargs :xxx +foo+)) TEST CL-USER> (progn (make-condition 'test) t) ...gives the error "oops"! ** Affects: sbcl Importance: Medium Status: Confirmed ** Tags: ansi -- DEFINE-CONDITION and constant :DEFAULT-INITARGS https://bugs.launchpad.net/bugs/539517 You received this bug notification because you are a member of SBCL hackers, which is subscribed to SBCL. Status in Steel Bank Common Lisp: Confirmed Bug description: CL-USER> (defconstant +foo+ (lambda () (error "oops"))) +FOO+ CL-USER> (define-condition test () ((xxx :initarg :xxx)) (:default-initargs :xxx +foo+)) TEST CL-USER> (progn (make-condition 'test) t) ...gives the error "oops"!

2 1

March snapshot
by Raymond Toy 08 Mar '10

08 Mar '10

The March snapshot has been tagged (snapshot-2010-03). Binaries will be uploaded soon. There are a few bug fixes, but the most critical one is that multiplication of a complex single-float by a single-float (with SSE2) produces the wrong result. This is fixed. Ray

1 0

Feb snapshots tagged
by Raymond Toy 04 Mar '10

04 Mar '10

The February snapshot has been tagged. Binaries will be uploaded soon. Starting with this snapshot, only Solaris 10 binaries will be uploaded; support for Solaris 8 is dropped. This also includes a change to TRANSLATE-PATHNAMES. See the release notes for details. Ray

4 8