March 2011 - armedbear-devel - mailman3.common-lisp.net

[armedbear-devel] Spaces in pathnames (jar:file:/x/y/z/a space/...)
by Theam Yong Chew 11 Jul '11

11 Jul '11

Dear ABCL developers, While ABCL can handle spaces (& others) in file pathnames just fine, a space in jar file pathnames still doesn't work. I have confirmed this on Linux, Mac and Windows. An example using Cygwin, $ java -jar abcl.jar Armed Bear Common Lisp 0.24.0 Java 1.6.0_20 Sun Microsystems Inc. Java HotSpot(TM) Client VM Low-level initialization completed in 0.625 seconds. Startup completed in 4.438 seconds. Type ":help" for a list of available commands. CL-USER(1): (load "jar:file:e:/My Dropbox/temp/a space/hello.jar!/hello.abcl") #<THREAD "interpreter" {9AC0F5}>: Debugger invoked on condition of type FILE-ERROR Failed to create URI from 'e:/My Dropbox/temp/a space/hello.jar': Illegal character in opaque part at index 10: file:e:/My Dropbox/temp/a space/hello.jar Restarts: 0: TOP-LEVEL Return to top level. (and yeah, this particular path already has a space character in "My Dropbox" along with my original intended "a space" folder) By the way, thanks for the :wildcard directory support (I've only just tested that, it works for me now!). Yong.

4 15

[armedbear-devel] The value :LONG is not of type (MEMBER NIL :BOOLEAN)
by Chun Tian (binghe) 30 May '11

30 May '11

Hi, ABCL developers I found my program have some CLOS code which could get the weakness of ABCL ... It's cl-net-snmp [1], which I just release a whole new version few days ago. My goal on ABCL is to make sure the server-side version (a pure Lisp SNMP Agent) run as a separated thread in JVM, so that people can use my program to remotely monitor any Java (or ABCL) servers. (I know some ABCL people are fixing bordeaux-threads, I'm watching this work and hope it could be done soon) Now I need help. If one could spend 5 minutes do a SVN checkout of the release branch: https://cl-net-snmp.svn.sourceforge.net/svnroot/cl-net-snmp/snmp/branches/6 and try to ASDF load it (you'll need usocket 0.5 and ironclad), two major CLOS bug of ABCL will show up, one is at "pdu.lisp", as what the mail title said, The value :LONG is not of type (MEMBER NIL :BOOLEAN). I have no idea how to fix it. Regards, Chun Tian (binghe) [1] http://common-lisp.net/project/cl-net-snmp/snmp.html Below are the error outputs when compiling a lisp file from cl-net-snmp: #<THREAD "interpreter" {24CCF86}>: Debugger invoked on condition of type TYPE-ERROR The value :LONG is not of type (MEMBER NIL :BOOLEAN). Restarts: 0: TRY-RECOMPILING Try recompiling pdu 1: RETRY Retry compiling component ("snmp" "pdu"). 2: ACCEPT Continue, treating compiling component ("snmp" "pdu") as having been successful. 3: TOP-LEVEL Return to top level. [1] SNMP(2): :bt 0: (SYSTEM:BACKTRACE) 1: (INVOKE-DEBUGGER #<TYPE-ERROR {6BA52C90}>) 2: (JVM::COMPILE-FORM #<JVM::LET/LET*-NODE {2910D926}> JVM::STACK :LONG) 3: (JVM:COMPILE-DEFUN NIL (LAMBDA (MOP::ARGS MOP::NEXT-EMFUN) (DECLARE (IGNORE MOP::NEXT-EMFUN)) (LET ((SNMP::PDU (%CAR MOP::ARGS))) (DECLARE (IGNORABLE SNMP::PDU)) (DECLARE (IGNORABLE SNMP::PDU)) (BLOCK SNMP::GENERATE-REQUEST-ID (WITH-SLOTS (SNMP::REQUEST-ID-COUNTER) SNMP::PDU (THE (UNSIGNED-BYTE 32) (LOGAND (PORTABLE-THREADS:ATOMIC-INCF SNMP::REQUEST-ID-COUNTER) 4294967295)))))) NIL "/Users/binghe/.cache/common-lisp/abcl-0.26.0-dev-svn-13251-fasl37-macosx-java/Users/binghe/Lisp/packages/snmp/ASDF_TMP_pdu_6.cls" #<FILE-STREAM {6539DEFE}> NIL) 4: (#<FUNCTION {753896F2}>) 5: (JRUN-EXCEPTION-PROTECTED #<FUNCTION {753896F2}>) 6: (SYSTEM::C-E-M-1 (MOP::ENSURE-METHOD 'SNMP::GENERATE-REQUEST-ID :LAMBDA-LIST '(SNMP::PDU) :QUALIFIERS 'NIL :SPECIALIZERS (LIST 'SNMP::COMMON-PDU) :FUNCTION #'(LAMBDA (MOP::ARGS MOP::NEXT-EMFUN) (DECLARE (IGNORE MOP::NEXT-EMFUN)) (LET ((SNMP::PDU (%CAR MOP::ARGS))) (DECLARE (IGNORABLE SNMP::PDU)) (DECLARE (IGNORABLE SNMP::PDU)) (BLOCK SNMP::GENERATE-REQUEST-ID (WITH-SLOTS (SNMP::REQUEST-ID-COUNTER) SNMP::PDU (THE (UNSIGNED-BYTE 32) (LOGAND (PORTABLE-THREADS:ATOMIC-INCF SNMP::REQUEST-ID-COUNTER) 4294967295)))))) :FAST-FUNCTION #'(LAMBDA (SNMP::PDU) (DECLARE (IGNORABLE SNMP::PDU)) (BLOCK SNMP::GENERATE-REQUEST-ID (WITH-SLOTS (SNMP::REQUEST-ID-COUNTER) SNMP::PDU (THE (UNSIGNED-BYTE 32) (LOGAND (PORTABLE-THREADS:ATOMIC-INCF SNMP::REQUEST-ID-COUNTER) 4294967295)))))) :FUNCTION) 7: (SYSTEM::CONVERT-ENSURE-METHOD (MOP::ENSURE-METHOD 'SNMP::GENERATE-REQUEST-ID :LAMBDA-LIST '(SNMP::PDU) :QUALIFIERS 'NIL :SPECIALIZERS (LIST 'SNMP::COMMON-PDU) :FUNCTION #'(LAMBDA (MOP::ARGS MOP::NEXT-EMFUN) (DECLARE (IGNORE MOP::NEXT-EMFUN)) (LET ((SNMP::PDU (%CAR MOP::ARGS))) (DECLARE (IGNORABLE SNMP::PDU)) (DECLARE (IGNORABLE SNMP::PDU)) (BLOCK SNMP::GENERATE-REQUEST-ID (WITH-SLOTS (SNMP::REQUEST-ID-COUNTER) SNMP::PDU (THE (UNSIGNED-BYTE 32) (LOGAND (PORTABLE-THREADS:ATOMIC-INCF SNMP::REQUEST-ID-COUNTER) 4294967295)))))) :FAST-FUNCTION #'(LAMBDA (SNMP::PDU) (DECLARE (IGNORABLE SNMP::PDU)) (BLOCK SNMP::GENERATE-REQUEST-ID (WITH-SLOTS (SNMP::REQUEST-ID-COUNTER) SNMP::PDU (THE (UNSIGNED-BYTE 32) (LOGAND (PORTABLE-THREADS:ATOMIC-INCF SNMP::REQUEST-ID-COUNTER) 4294967295)))))))

3 13

[armedbear-devel] json-rpc?
by Axel Rauschmayer 27 Apr '11

27 Apr '11

I think ABCL would make an excellent Ajax server. As such, it would have to support json-rpc. Any suggestions as to how to make this happen? The first part is obviously the server, where the two choices that I can see are Hunchentoot and a servlet container such as Tomcat. In the latter case, I would expect to use a technique like abcl-web (which seems a little bit complicated, but doable). The second part is the JSON parsing. How would I do that? Via CL-JSON? Via Yason? Via a Java library? Sorry for these newbie questions. I’m just getting started with Common Lisp and ABCL. Thanks, Axel -- Axel.Rauschmayer(a)ifi.lmu.de http://www.pst.ifi.lmu.de/~rauschma/

4 10

[armedbear-devel] Fwd: ASDF 2.014 released
by Faré 28 Mar '11

28 Mar '11

[Note: I have skipped ECL and Allegro maintainers from the notification, since I know they subscribe to the announcement. You too can subscribe to the asdf-announce mailing-list or its gmane mirror gmane.lisp.asdf.announce and ask me to take your list off the Cc:] ---------- Forwarded message ---------- From: Faré <fahree(a)gmail.com> Date: 28 March 2011 14:08 Subject: ASDF 2.014 released To: asdf-announce(a)common-lisp.net, ASDF-devel <asdf-devel(a)common-lisp.net> Dear ASDF users, I just blessed ASDF 2.013.7 as 2.014. As compared to 2.013, it includes a significant quality item that makes it essential for everyone who distributes ASDF without an implementation (e.g. Quicklisp). It also includes better SCL support, cosmetic improvements, and robustification of some corner cases. Tests have been added to prevent the regressions observed in the 2.013 release. * Fixed bug preventing upgrade from 2.000 to 2.008 (test added) * Better support for URL pathnames on SCL (test added) * Robustified defsystem-depends-on * Cosmetic changes: * better more portably readable error messages. * remove forward references, again (test added) * canonicalize system names earlier (slight robustness improvement) As usual, I invite people who distribute ASDF to update the version they ship, be it with their implementations, with their software distribution, etc. Happy Happy Joy Joy [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] "Don't worry about people stealing your ideas. If your ideas are any good, you'll have to ram them down people's throats." — Howard Aiken

2 1

[armedbear-devel] Improvements to our Gray streams implementation
by Mark Evenson 28 Mar '11

28 Mar '11

As part of the long continuing road to Hunchentoot, I am pleased to announce that with [r13255][1], ABCL can now pass the flexi-streams-1.0.7 test suite as long as [trivial-gray-streams is patched to recognize the new FILE-POSITION generic][2]. [1]; http://trac.common-lisp.net/armedbear/changeset/13255 [2]: http://detroit.slack.net/~evenson/abcl/trivial-gray-streams-abcl-20110320a.… -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

1 1

[armedbear-devel] Patches for metatilities-base and lift
by Mark Evenson 22 Mar '11

22 Mar '11

Patches to get [metatilities-base][1] and [lift][2] as distributed by Quicklisp MAR2011. We really need to either a) make our own Quicklisp distribution or (my preference) b) make a QUICKLISP-PATCH system to apply patches as QL:QUICKLOAD happens. [1]: http://detroit.slack.net/~evenson/abcl/metatilities-base-20101006-darcs-abc… [2]: http://detroit.slack.net/~evenson/abcl/lift-20110320-git-abcl-20110322.diff -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

3 8

Re: [armedbear-devel] [Bordeaux-threads-devel] [Updated4] Patch for ABCL against BORDEAUX-THREADS HEAD
by Chun Tian (binghe) 21 Mar '11

21 Mar '11

Hi, Mark I'm interesting in your work. First, I'd like to know, how to do a "condition variable wait with timeout" with your exist work, Second, do you think it's possible to make ABCL supporting some atomic operations, something like ATOMIC-INCF or ATOMIC-PUSH, this can be very useful to implement some lockless algorithms. Regards, Chun Tian (binghe) 在 2011-3-18，15:50， Mark Evenson 写道： > On 3/2/11 8:50 PM, Martin Simmons wrote: > >> I think that the implementation of condition-wait has some major problems: > > Thanks very much for the comments. > > I have an [updated patch][1] that attempts to address these issues for > further review for inclusion in BORDEAUX-THREADS. > > [1]: > http://detroit.slack.net/~evenson/abcl/bordeaux-threads-abcl-20110318a.diff > >> 1) If no other threads are trying to claim the lock, then condition-wait will >> return immediately rather than waiting. > > I couldn't reproduce this behavior. In ABCL, the THREADS:OBJECT-WAIT > implementation is mainly a simple wrapping of the underlying > [java.lang.Object.wait()][2] which clearly should wait. > > [2]: > http://download.oracle.com/javase/6/docs/api/java/lang/Object.html#wait%28%… > >> 2) If two threads are waiting in condition-wait and two other threads call >> condition-notify, then it is possible that only one thread will return from >> condition-wait because the call to acquire-lock in one of them might return >> nil causing it to wait again. > > The DO looping construct has been replaced with a simpler subsequent > BT:ACQUIRE-LOCK that should solve this bug. > >> 3) If condition-notify is called by one thread when a waiting thread is just >> about to enter the threads:synchronized-on form (but before it gets >> synchronized), then the notify will be lost. This happens because the >> underlying threading primitives have no "memory" of calls to notify when >> nothing it waiting (which is also the expected semantics for POSIX condition >> variables BTW). > > THREADS:SYNCHRONIZED-ON is now the first form executed by > BT:CONDITION-WAIT so the window here is considerably narrowed. > >> Also, I think condition-notify should be using threads:object-notify rather >> than threads:object-notify-all. > > We now use THREADS:OBJECT-NOTIFY. > > > > > -- > "A screaming comes across the sky. It has happened before, but there > is nothing to compare to it now." > > > _______________________________________________ > Bordeaux-threads-devel mailing list > Bordeaux-threads-devel(a)common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/bordeaux-threads-devel

3 3

[armedbear-devel] ASDF 2.013 released
by Faré 20 Mar '11

20 Mar '11

Dear Armed Bear developers, congratulations for your many releases since I last contacted you. I've just released ASDF 2.013. I don't know which version you're using, but there have been numerous small bug fixes and improvements in ASDF. For the sake of sharing those improvements, I think it would be a good time to push ASDF to all Lisp implementations. Could you include it in yours? While abcl is used as part of my automated test suite, I don't often upgrade my abcl copy (currently 0.22.0) -- it would help if there were a debian package. Please make sure ASDF suits your purposes, and contact me with any patch you use for inclusion upstream. PS: I created a mailing-list asdf-announce. Maybe someone amongst you could join it, so I don't need to push my announces to this mailing-list. Or maybe I can just Cc: my announce to this mailing-list and not bother with further explanations? [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] The common argument that crime is caused by poverty is a kind of slander on the poor. — H. L. Mencken ---------- Forwarded message ---------- From: Faré <fahree(a)gmail.com> Date: 20 March 2011 00:29 Subject: ASDF 2.013 released To: asdf-announce(a)common-lisp.net Dear Common Lisp Users, I just blessed ASDF 2.012.12 as 2.013. It includes many small improvements since previous release, for portability, robustness, usability. For the sake of making these improvements available to all users, I invite all vendors and packagers to update their software to include this latest release. Improvements since 2.012: * Fixes and cleanups for CLISP, ECL, SBCL. * Added support for two legacy platforms: (R)MCL, Genera * Cleanup features: now using #+asdf-unix and #+asdf-window * Many cleanups and improvements regarding our portable pathname layer * Fixes a regression in source-registry scanning from 2.011.4 * Remember *source-registry-parameter* and *output-translations-parameter* * Export and document coerce-pathname (f.k.a merge-component-name-type) * allow description and long-description for all components * Several documentation updates Happy hacking, [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] I hold that America, Champion of the World is a betrayal of its humble beginnings as One Nation Underdog.

2 2

Re: [armedbear-devel] [Updated4] Patch for ABCL against BORDEAUX-THREADS HEAD
by Mark Evenson 18 Mar '11

18 Mar '11

On 3/18/11 4:41 PM, Ville Voutilainen wrote: > On 18 March 2011 17:37, Mark Evenson<evenson(a)panix.com> wrote: >> This was the previous implementation, which was the subject of the >> criticism: >> >> (defun condition-wait (condition lock) >> (check-type condition condition-variable) >> (release-lock lock) >> (do () >> ((acquire-lock lock nil)) >> (threads:synchronized-on condition >> (threads:object-wait condition)))) > > If this is directly mapped to a pthread implementation, the loop must be there. I think it is slightly different, as the semantics of BT:CONDITION-WAIT are merely that the lock is always reacquired before returning. The caller of BT:CONDITION-WAIT is required to check for spurious wakeups. > >> I believe the race condition is on the the synchronization on the condition >> variable, not on the mutex lock. > > The condition variable needs to use the mutex lock given, not a separate lock. The condition variable interface is using the mutex lock specified in BT:CONDITION-WAIT. For the ABCL implementation, I'm using the Java monitor associated with the condition variable for the additional synchronization needed to implement BT:CONDITION-NOTIFY which couldn't use the mutex lock without contention problems. But definitely check my logic here, as it has been faulty before. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

2 3

Re: [armedbear-devel] [Updated4] Patch for ABCL against BORDEAUX-THREADS HEAD
by Mark Evenson 18 Mar '11

18 Mar '11

On 3/2/11 8:50 PM, Martin Simmons wrote: > I think that the implementation of condition-wait has some major > problems: Thanks very much for the comments. I have an [updated patch][1] that attempts to address these issues for further review for inclusion in BORDEAUX-THREADS. [1]: http://detroit.slack.net/~evenson/abcl/bordeaux-threads-abcl-20110318a.diff > 1) If no other threads are trying to claim the lock, then > condition-wait will return immediately rather than waiting. I couldn't reproduce this behavior. In ABCL, the THREADS:OBJECT-WAIT implementation is mainly a simple wrapping of the underlying [java.lang.Object.wait()][2] which clearly should wait. [2]: http://download.oracle.com/javase/6/docs/api/java/lang/Object.html#wait%28%… > 2) If two threads are waiting in condition-wait and two other threads > call condition-notify, then it is possible that only one thread will > return from condition-wait because the call to acquire-lock in one of > them might return nil causing it to wait again. The DO looping construct has been replaced with a simpler subsequent BT:ACQUIRE-LOCK that should solve this bug. > 3) If condition-notify is called by one thread when a waiting thread > is just about to enter the threads:synchronized-on form (but before > it gets synchronized), then the notify will be lost. This happens > because the underlying threading primitives have no "memory" of > calls to notify when nothing it waiting (which is also the expected > semantics for POSIX condition variables BTW). THREADS:SYNCHRONIZED-ON is now the first form executed by BT:CONDITION-WAIT so the window here is considerably narrowed. > Also, I think condition-notify should be using threads:object-notify > rather than threads:object-notify-all. We now use THREADS:OBJECT-NOTIFY. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

3 5