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

[armedbear-devel] COMPILE-SYSTEM and file dependencies
by Tobias C. Rittweiler 03 Mar '10

03 Mar '10

How much of a full CL is available for COMPILE-SYSTEM? Have you contemplated using (perhaps a stripped down version of) ASDF for specifying the exact dependencies for the *.lisp files? Getting that right in a descriptive manner is important as the system grows otherwise you end up with a mess like in SBCL where a mere mortal has no idea what in the build may break if you change something. -T.

1 0

[armedbear-devel] tentative patch: extensible sequences (following the same protocol as SBCL)
by Alessio Stalla 02 Mar '10

02 Mar '10

Greetings everyone, I'm happy to announce that I have a preliminary version of user-extensible sequences working on ABCL, following the protocol proposed and implemented by Christophe Rhodes on SBCL ("User-extensible sequences in Common Lisp", http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.65.1604&rep=rep1&t…) This includes: - the possibility for the user to write subclasses of CL:SEQUENCE - all functions operating on sequences have a corresponding generic function in the SEQUENCE package that is called on user-defined sequence types, and for which the user can write methods to implement his/her custom sequences - make-sequence works with user-defined sequences (using sequence:make-sequence-like as in SBCL) - mop::class-prototype has been added (as a tiny wrapper around mop::allocate-instance) - iterating over user-defined sequences integrated with LOOP (untested, but should work as our loop implementation is derived from CMUCL like SBCL's) - MAP and MAP-INTO should work unchanged limitations/things missing wrt. SBCL (that I know of): - no integration with DOSEQUENCE - to use extensible sequences you must explicitly (require :extensible-sequences) in advance - much less attention to precise sequence type information (but probably my patch doesn't improve nor worsen the situation before it) the patch doesn't seem to break any new ANSI tests; however I've tested the extensible sequences proper very lightly, and I don't consider the patch ready for trunk yet. My long-term goal is to use the new extensible sequences support to make Java collections be Lisp sequences. That should include Clojure collections as well, since afaik they implement the Collection API. If anyone has comments or critiques, or wants to help, you're welcome. Cheers, Alessio

2 3

[armedbear-devel] Synthetic Method Removal
by dmiles＠users.sourceforge.net 02 Mar '10

02 Mar '10

This is the .patch file that removes synthetic access to private fields/constructors and methods. Its intention is to make stack traces easier to read. And will have a miniscule speedup. And shrink classfile sizes 1-4%

1 0

[armedbear-devel] Unfair fresh-line.5 ANSI-TEST?
by dmiles＠users.sourceforge.net 01 Mar '10

01 Mar '10

Fresh-line.5 is a when we compare the output string againt a string read from the file.. this means the test is contigent on the line ending style of ABCL matching what SVN checkout did. (deftest (let (result) (values (with-output-to-string (s) (write-char #\Space s) (setq result (list (multiple-value-list (notnot-mv (fresh-line s))) (multiple-value-list (fresh-line s)) (multiple-value-list (fresh-line s))))) result)) " " ((t) (nil) (nil))) I am thinking the compared to litteral needs to be a constant programmatily contructed. Such as a write-char #\Space + write-char #\Newline Any thoughts of patch ideas for the ansi-tests?

1 0