armedbear-devel

armedbear-devel@common-lisp.net

1 participants
1200 discussions

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

[armedbear-devel] closure-html compiling again (was Re: SVN r13600 breaks clean trunk Build)
by Mark Evenson 21 Oct '11

21 Oct '11

On Sep 20, 2011, at 15:51 , Erik Huelsmann wrote: > Hi Mark, > > On Tue, Sep 20, 2011 at 11:22 AM, Mark Evenson <evenson.not.org(a)gmail.com> wrote: > > On Sep 20, 2011, at 10:34 , ehuels(a)gmail.com wrote: > > > Hi Mark, > > > > You fixed it already, I see. Sorry about the breakage. Which library fails next? :-) > > > > Unfortunately, I'm having problems compiling closure-common (closure-common-20101107-git), upon which closure-html depends: > With the abcl-1.0.x branch, closure-html from Quicklisp is compiling again.

1 0

[armedbear-devel] packaging of abcl 0.27.0
by Ljungberg, Magnus - 0661 - MITLL 21 Oct '11

21 Oct '11

In the past you've published abcl as a maven artifact over at sonatype.org, something I benefit from daily for my project. Can you please continue that for new releases? Thanks Magnus Ljungberg

4 3

[armedbear-devel] Maxima, once again
by Reinhard Oldenburg 21 Oct '11

21 Oct '11

Hi everybody, I check the staus of ABCL every few month to see how well it runs Maxima. The findings are, that .... - The testsuite goes through, but ABL is more then 10 times slower than native Lisps. - However, tehre are problems with several packages, e.g. load(fmin_cobyla); fails - Loading Maxima with ASDF fails. - There is still no way to produce an image file. Last year I was told that ABCL can load from URL, but I fear that doing this takes a couple of days 8which I can't afford). So is seems that there is not yet a good way to write Applets using Maxima. If anyone can produce a maxima.jar, I'd be happy. Any comments? reinhard

2 1

[armedbear-devel] abcl-1.0 -- The Manual
by Mark Evenson 23 Sep '11

23 Sep '11

We have always informally answered the question as to when ABCL would deserve a 1.0 release number when it was a conforming ANSI implementation. Since we are more or less ANSI complete at this point from a feature standpoint with the recent implementation of the long form of DEFINE-METHOD-COMBINATION, it makes some sense to push for an ABCL 1.0 release which we could potentially announce at ECLM 2011, since Erik, Alessio, and I will attend. The [CLHS outlines the requirements for conforming implementation][1] as including […] 1.5.1.2 Documentation of Implementation-Dependent Features 1.5.1.3 Documentation of Extensions […] 1.5.1.5 Conformance Statement […] [1]: http://www.lispworks.com/documentation/HyperSpec/Body/01_ea.htm To this end, I started an [ABCL manual written in LaTex][2]. With LaTeX we have the ability to include diagrams rather easily, something that despite Texinfo's claims to the contrary, I think should not be prohibited in documentation. I have not found a suitable LaTex2HTML translator (although many exist), but would probably approach this as a problem to be addressed after we produce an initial manual. [2]: http://trac.common-lisp.net/armedbear/browser/trunk/abcl/doc/manual To render the manual in PDF, install [TeX Live 2011][3], and simply issue cmd$ pdflatex abcl.tex in a the manual directory. [3]: http://www.tug.org/texlive/ The structure of the manual is roughly in place, from which I have been cribbing ideas from the [SBCL][4] and [CCL][5] manuals [4]: http://www.sbcl.org/manual/ [5]: http://ccl.clozure.com/ccl-documentation.html but have still not committed to a final structure. I have started to create LaTeX macros in 'abcl.sty' to create an environment in which contributors can work on the manual without necessarily understanding that much of LaTeX by creating a semantics/presentation layer. Currently, this mostly consists of ways of marking up text as being Lisp, Java, or Shell source code. I plan to at least to produce a method to indicate that text refers to a given Lisp symbol in a given package so a reasonable cross referencing system can produce an index and page references. A tension exists in the current effort between being a manual, and a tutorial with examples. I would propose we concentrate on the manual aspects, while allowing inclusion of examples as the existing text gives a pretty reasonable introduction to extending ABCL via Java that would be a shame to lose. But I could be persuaded to remove or move to an appendix if we wanted to emphasize concision. Since TeX easily allows comments in documents with '%' characters, one can find various notes and ideas present in the current document to bring one up to speed on what I have in mind. I intend to document the JAVA, EXTENSIONS, and SYSTEM packages by adding doctstrings to out implementation for all exported symbols, following the convention that there should be a short synopsis statement for the function as the first sentence, followed by a newline, followed by more explicit text. I intend to write a Lisp tool that "scrapes" these docstrings from a live ABCL process, transforming into the appropriate LaTeX source which we would then include in the manual. This isn't sufficient but necessary in my opinion to meet the criteria of documenting implementation dependent features. If someone wished to help, getting our exported docstrings in order would be a task somewhat orthogonal to the production of the manual. So, I would invite potential contributors to the manual to look at the source, build the PDF version, and consider what sections they would like to tackle. Then we can divide this manual up into sections by file, so people can work somewhat in isolation. As an informal deadline, I think we should have a plan in place by October 1 to have a chance of finishing things by ECLM 2011. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

1 0

[armedbear-devel] FASL Format bump on trunk
by Erik Huelsmann 20 Sep '11

20 Sep '11

Everybody running off trunk should be warned that I just updated the FASL format number: the fixes for CLOSURE-HTML changed the format in a backward incompatible way. The new format number is 38, the old one 37. Format bumps are relatively rare and format 37 has been in use for quite a while now. I'm sorry for the inconvenience caused, if any. Bye, Erik.

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel