armedbear-ticket November 2008

armedbear-ticket@common-lisp.net

1 participants
27 discussions

Re: [armedbear-ticket] [armedbear] #7: SLIME support (delivered with ABCL) needs updating
by armedbear 02 Nov '08

02 Nov '08

#7: SLIME support (delivered with ABCL) needs updating -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: defect | Status: assigned Priority: minor | Milestone: Component: component1 | Version: Resolution: | Keywords: -------------------------+-------------------------------------------------- Comment(by ehuelsmann): Removal of the files mentioned above has been completed in commit r11375. It would be interesting to see to what extent ABCL needs to be modified to work with swank-gray.lisp. As soon as it does, the classes SlimeInputStream and SlimeOutputStream can be removed. -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/7#comment:5> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 0

Re: [armedbear-ticket] [armedbear] #7: SLIME support (delivered with ABCL) needs updating
by armedbear 02 Nov '08

02 Nov '08

#7: SLIME support (delivered with ABCL) needs updating -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: defect | Status: assigned Priority: minor | Milestone: Component: component1 | Version: Resolution: | Keywords: -------------------------+-------------------------------------------------- Changes (by mevenson): * owner: mevenson => ehuelsmann * priority: major => minor Comment: I've been running (and rebuilding) ABCL and SLIME for a week or so without the files {{{ slime-loader.lisp slime.lisp swank-abcl.lisp swank-loader.lisp swank-protocol.lisp swank-xcl.lisp swank-allegro.lisp swank-package.lisp swank-sbcl.lisp swank.lisp }}} The attached patch removes them from the tree. Reassigning to Erik to remove from trunk. -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/7#comment:4> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 0

Re: [armedbear-ticket] [armedbear] #14: Support for a C-calling FFI for CFFI to build upon
by armedbear 02 Nov '08

02 Nov '08

#14: Support for a C-calling FFI for CFFI to build upon --------------------------+------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: Component: component1 | Version: Resolution: | Keywords: --------------------------+------------------------------------------------- Comment(by mevenson): For #14, I didn't know JNA either, but essentially it seems to be just what I thought to be necessary in my first mail --- a generic JNI stub that builds a stack frame and calls an arbitrary C function. Since it builds on top of JNI, you should be able to use it with existing JRE/JDK editions. If you do use JNA, it would become a requisite for the yet-to-be-seen ffi for abcl. -- Hideo at Yokohama via armedbear-j-devel -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/14#comment:2> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 0

Re: [armedbear-ticket] [armedbear] #14: Support for a C-calling FFI for CFFI to build upon
by armedbear 02 Nov '08

02 Nov '08

1 0

Re: [armedbear-ticket] [armedbear] #13: Support for (FLEXI-STREAMS-like) :external-format
by armedbear 02 Nov '08

02 Nov '08

#13: Support for (FLEXI-STREAMS-like) :external-format -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Resolution: | Keywords: -------------------------+-------------------------------------------------- Comment(by mevenson): For #13 I looked at FileStream.java . If the _setFilePosition is required even for character streams, I think there is no easy and safe way to implement multiple encoding handling. But since abcl can read from network connections, on which you can't do random access, I believe there is a way to keep the seeking requirement out of the way of character (non-binary) streams. -- Hideo at Yokohama via armedbear-j-devel -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/13#comment:2> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 0

Re: [armedbear-ticket] [armedbear] #11: Integration of invoke.lisp, dynamic dispatch of java methods
by armedbear 01 Nov '08

01 Nov '08

1 0

Re: [armedbear-ticket] [armedbear] #11: Integration of invoke.lisp, dynamic dispatch of java methods
by armedbear 01 Nov '08

01 Nov '08

#11: Integration of invoke.lisp, dynamic dispatch of java methods --------------------------+------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: enhancement | Status: new Priority: minor | Milestone: Component: component1 | Version: Resolution: | Keywords: --------------------------+------------------------------------------------- Comment(by mevenson): This ticket references Alan Ruttenberg's [invoke.lisp][1], which uses the [JScheme implementation][2] to dynamically dispatch method calls. This entails having the 'jscheme.jar' in ABCL's invoked classpath. The property 'additional.jars' in the Ant based build system can be used to include such jars in the ABCL wrapper script. [1]: http://svn.mumble.net:8080/svn/lsw/trunk/jss/invoke.lisp [2]: http://jscheme.sourceforge.net/jscheme/main.html -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/11#comment:1> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-ticket November 2008