armedbear-devel October 2011

armedbear-devel@common-lisp.net

12 participants
13 discussions

[armedbear-devel] destroy-thread and unwind-protect
by James Lawrence 08 Aug '12

08 Aug '12

(defun test-cleanup () (let* ((cleanedp nil) (thread (threads:make-thread (lambda () (unwind-protect (sleep 999) (setf cleanedp t)))))) (sleep 0.5) (threads:destroy-thread thread) (sleep 0.5) cleanedp)) (test-cleanup) ABCL-1.0.0 and ABCL-0.27.0 return NIL. Other implementations I tested all return T -- Allegro, Clozure, LispWorks, SBCL (changing "threads" to "bordeaux-threads"). Of course this isn't a bug since ABCL is free to do what it wishes. Does ABCL wish that?

5 5

[armedbear-devel] Manual format
by Blake McBride 29 Oct '11

29 Oct '11

Greetings, I was looking at the ABCL manual for ABCL 1.0 under the 'manual' directory. I noticed that it is in LaTeX format. I have been using TeX, LaTeX and Texinfo for many years. Among many other things, I have written two longish user manuals in Texinfo. They are located (including source) at: http://blake.mcbride.name/software/dynace/downloads.html under the 'manual' directory. With the experience I've had with TeX, LaTeX, and Texinfo, I feel very strongly that these are unbelievably great tools, and, in fact, the right tools for the job. However, I also feel strongly that Texinfo is the better format for the particular task of a manual on ABCL. I use LaTeX pretty often, but I have found Texinfo better suited for user manuals of computer topics for several reasons. First, the macros defined are more natural for the topic. Second, Texinfo supplies much better index creation tools for functions, variables, classes, etc.. Lastly, if you use Texinfo, you get online documentation for free! Texinfo is specifically designed for exactly this kind of technical document. LaTeX is equally good, but at writing non-technical books. Latex is not a natural fit for technical documents in my opinion. So, in conclusion: 1. I recommend switching to Texinfo. It would be especially easy at this early juncture. 2. The manuals I wrote come out, IMO, nicely. These documents could be used as templates. 3. My time is a real problem but I think I can convert the existing document so that you'd have it all setup to continue with if that is desired. I welcome your thoughts. Blake McBride

4 4

[armedbear-devel] FSet on ABCL
by Alessio Stalla 26 Oct '11

26 Oct '11

Greetings, as part of my nth plan to conquer the world (which of course I won't unveil right now), I tried FSet on ABCL. I managed to make it run, but I had to patch it; you can find the patch attached (it's taken against the version in Quicklisp, but I believe it's the latest version). Besides some minor #+abcl porting stuff, the one thing that stuck out was the DEFLEX macro for defining global lexical variables, which conflicts with ABCL's implementation of symbol macros. (deflex var) expands basically into (define-symbol-macro var (symbol-value 'var)). The problem: ABCL stores symbol macros in the value cell of symbols, so you can't have a symbol which is both a variable and a symbol macro. Now, I believe deflex as written is non portable CL. This is because accessing the symbol-value of an unbound variable is, to my interpretation, unspecified [*]; and if you use defvar/defparameter with var, then you cannot use it as a symbol macro. Thus, I patched it (taking inspiration from Rob Warnock's version of deflex/defglobal). However, I do think ABCL's implementation is very brittle (and probably conflicting with ANSI as well), because if you setf the symbol-value of a symbol with a global symbol macro attached, you remove the symbol macro! So, I think we should fix it for 1.0.1. Perhaps I can do the fix myself, but we better discuss it before because I fear this might be a deep change. [*] symbol-value ... Accesses the symbol's value cell. [1] value cell n. Trad. (of a symbol) The place which holds the value, if any, of the dynamic variable named by that symbol, and which is accessed by symbol-value. [2] dynamic variable n. a variable the binding for which is in the dynamic environment. [3] I don't think a symbol for which there is no special declaration in scope can be considered to name a dynamic variable, and thus to have a value cell at all. [1] http://www.lispworks.com/documentation/HyperSpec/Body/f_symb_5.htm#symbol-v… [2] http://www.lispworks.com/documentation/HyperSpec/Body/26_glo_v.htm#value_ce… [3] http://www.lispworks.com/documentation/HyperSpec/Body/26_glo_d.htm#dynamic_… Cheers, Alessio

1 0

[armedbear-devel] Support for specialized arrays?
by Blake McBride 26 Oct '11

26 Oct '11

Greetings, I presume ABCL supports specialized arrays (element-type:) syntactically but I am wondering if ABCL actually creates more efficient, type specific, arrays rather than generic, arrays of objects? Thanks. Blake McBride

3 3

Re: [armedbear-devel] bug of resolve-symlinks
by Gábor Balázs 25 Oct '11

25 Oct '11

hY, I think there is a bug in the list-directory function. The resolve-symlinks flag seems to always resolve the directory symlinks even when the flag is set to nil. Let's have a directory as : total 4 drwxr-xr-x 2 bege users 4096 Oct 23 23:52 dir lrwxrwxrwx 1 bege users 3 Oct 23 23:53 dir-link -> dir -rw-r--r-- 1 bege users 0 Oct 23 23:53 file lrwxrwxrwx 1 bege users 4 Oct 23 23:53 file-link -> file Then Armed Bear Common Lisp 0.26.2 Java 1.6.0_26 Sun Microsystems Inc. Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 1.436 seconds. Startup completed in 5.385 seconds. Type ":help" for a list of available commands. CL-USER(1): *(directory "./*" :resolve-symlinks nil)* (#P"/home/bege/TEST/./file" *#P"/home/bege/TEST/dir/"*#P"/home/bege/TEST/./file-link" *#P"/home/bege/TEST/dir/"*) Sorry, if this has been already fixed... Best, `bg`

2 1

Re: [armedbear-devel] destroy-thread and unwind-protect
by Mark Evenson 25 Oct '11

25 Oct '11

On Oct 24, 2011, at 17:59 , James Lawrence wrote: […] > Thanks for the response. > > That seems like a different issue. The purpose is not to guarantee > that the thread is destroyed. > > The behavior sought is: when the protected form stops executing, run > the cleanup forms. […] > In my case I am only interested in detecting the termination of a > thread without polling. Maybe there is an ABCL-specific way to do > that. THREADS:THREAD-ALIVE-P Function: Boolean predicate whether THREAD is alive.

2 4

[armedbear-devel] asdf and windows vs unix on abcl
by Faré 24 Oct '11

24 Oct '11

ABCL is special in that it can run on either Windows or Unix. The problem is that ASDF 2.017 determines which of Windows or Unix at compile-time, which causes confusion when ABCL's builtin ASDF is compiled on Windows and used on Unix or vice-versa. And I can tell your binary was definitely produced on Windows. (I found this issue while testing cl-launch. I also noticed that you fixed your ext:*command-line-argument-list* albeit in a necessarily incompatible way.) I suppose the solution is that the test of unixness vs windowsness should happen at runtime. Crazy. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org

5 13

[armedbear-devel] Minor doc patch for table of contents
by Ville Voutilainen 22 Oct '11

22 Oct '11

The basic TOC should be simple. It seems that pdflatex automagically makes the TOC entries to be hyperlinks, so this should be a relative no-brainer? We can use a more elaborate toc-package later if need be. I haven't pushed this in yet, because the manual is sort-of-Mark's turf, so I'm getting my feet wet before committing directly. ;)

2 1

Re: [armedbear-devel] ABCL manual, PDF with suggestions
by Mark Evenson 21 Oct '11

21 Oct '11

On Oct 21, 2011, at 08:34 , Philipp Marek wrote: > Hello Mark, > > here's the ABCL manual with a few ;) annotations. > > Please take them with a grain of salt, yadda yadda yadda. Thanks a lot! There's a lot of detailed work that you point out that I didn't get a chance to finish, but I tried to incorporate your large-scale criticism in [the abcl-20111021a release of the Armed Bear Common Lisp User Manual][1]. The [LaTex sources to the manual][2] are on the abcl 1.0.x branch for which diffs are solicited. [1]: http://abcl-dynamic-install.googlecode.com/files/abcl-20111021a.pdf [2]: http://svn.common-lisp.net/armedbear/branches/1.0.x/abcl/doc/manual/abcl.tex

1 0

[armedbear-devel] abcl-1.0.x branched. Please test.
by Mark Evenson 21 Oct '11

21 Oct '11

In preparation for the release of ABCL-1.0.0 on October 22, 2011 I have [created the 1.0.x branch][1]. It seems to do pleasantly well under Java 7, so I have removed the compile time warning. [1]: svn://common-lisp.net/project/armedbear/svn/branches/1.0.x/abcl

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel October 2011