June 2009 - armedbear-ticket - mailman3.common-lisp.net

[armedbear-ticket] [armedbear] #44: Unboxing of local variables with :float and :double representations
by armedbear 15 Mar '10

15 Mar '10

#44: Unboxing of local variables with :float and :double representations -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: enhancement | Status: new Priority: major | Milestone: Component: compiler | Version: Keywords: | -------------------------+-------------------------------------------------- Currently, variables with :float or :double representations don't get stored unboxed. Since intermediate results of those types do get unboxed, this leads to additional boxing/unboxing. -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/44> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #48: SLIME CVS HEAD as of 2008-12-30 broken
by armedbear 05 Jan '10

05 Jan '10

#48: SLIME CVS HEAD as of 2008-12-30 broken -------------------------------------+-------------------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: 0.13 Component: other | Version: 1.0 Keywords: slime emacs application | -------------------------------------+-------------------------------------- Symptom is the failed listening to SlimeInputStream that doesn't detect a pipe close, therefore never closes, so further enviornment bindings are incorrect. *inferior-lisp* buffers needs to evaluate a form before SLIME works properly. Something messed up in the Stream ._finishOuput() calls?? -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/48> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #54: pprint.lisp incompatible with gray-streams.lisp
by armedbear 03 Nov '09

03 Nov '09

#54: pprint.lisp incompatible with gray-streams.lisp ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: other | Version: Keywords: | ------------------------+--------------------------------------------------- pprint.lisp special-cases the XP-STRUCTURE argument type for the stream argument specified to all the stream functions. Although SBCL uses largely the same approach, it uses a (slightly) different approach, which is important in the details. (Isn't that where the devil usually is?) The difference between ABCL and SBCL is that SBCL - although it uses largely the same structure to store its pprinter values - this structure extends the structure which is used to represent streams. In ABCL, this structure is a structure by itself. To compensate for the fact that the structure isn't recognised as a stream itself, all stream functions special case the XP-STRUCTURE argument handling. Proposed solution: make streams based on dispatch tables stored in structures, just as SBCL does. This way, most of our streams "stuff" can be implemented in Lisp, instead of Java. As a bonus, this issue can be resolved along the same lines as SBCL does. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/54> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #20: GRAY-STREAMS breaks ASDF loading
by armedbear 03 Nov '09

03 Nov '09

#20: GRAY-STREAMS breaks ASDF loading ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: defect | Status: new Priority: critical | Milestone: Component: component1 | Version: Keywords: | ------------------------+--------------------------------------------------- The sequence: (require 'asdf) (require 'gray-streams) (asdf:oos 'asdf:load-op :swank) breaks the asdf operation, while the same thing without the gray-streams works like a charm -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/20> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #49: Support loading of compiled functions off byte arrays
by armedbear 23 Oct '09

23 Oct '09

#49: Support loading of compiled functions off byte arrays -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: Component: other | Version: Keywords: | -------------------------+-------------------------------------------------- loadCompiledFunction() in Lisp.java loads bytes out of a file, then loads the "class-bytes" off the resulting byte array. The result being a loaded class. The goal of this issue is to expose this interface in order to eliminate the need for the compiler to write compiled functions out to files before loading them into the JVM. -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/49> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 1

Re: [armedbear-ticket] [armedbear] #12: Better support for java interaction (current java: package)
by armedbear 01 Jun '09

01 Jun '09

#12: Better support for java interaction (current java: package) --------------------------+------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: Component: other | Version: Resolution: | Keywords: --------------------------+------------------------------------------------- Comment(by trittweiler): This is the area that ABCL should try to polish itself and then advertise for it by writing documentation, including blogging to planet.lisp.org. It's always good to know the competition, so here's what Franz provides: http://www.franz.com/support/documentation/current/doc/jlinker.htm and http://www.franz.com/support/documentation/current/doc/jil.htm -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/12#comment:1> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 0