April 2008 - cl-debian@common-lisp.net - mailman3.common-lisp.net

[cl-debian] Bug#460444: cl-screen-sbcl: Wrong spelling in package description: SLang -> S-Lang
by Rafael Laboissiere 06 Apr '08

06 Apr '08

Package: cl-screen-sbcl Version: 1.0-4 Severity: minor The description of the package contains the word "SLang" referring to the S-Lang library. Please, fix the spelling such that it reads "S-Lang" instead. Correct spelling/capitalisation of project names is currently under discussion in debian-devel [1]. [1] http://lists.debian.org/debian-devel/2008/01/msg00304.html -- Rafael

2 1

[cl-debian] Bug#436641: cl-screen-sbcl has unmet recommends on some archs
by Robert Lemmen 06 Apr '08

06 Apr '08

Package: cl-screen-sbcl Severity: important Version: 1.0-4 User: debian-release(a)lists.debian.org Usertags: goal-recommends hi, cl-screen-sbcl has a recommends on sbcl, which is not available on all plattforms. since we want to install recommends by default in lenny, this needs to be addressed. the easiest way would be to change the recommends into a Recommends: sbcl (>= 0.9.3) [alpha amd64 i386 mips mipsel powerpc sparc]. thanks robert -- Robert Lemmen http://www.semistable.com

2 1

[cl-debian] Accepted cl-screen-sbcl 1.0-4.1 (source all)
by Amaya Rodrigo Sastre 06 Apr '08

06 Apr '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Sun, 30 Mar 2008 22:18:36 +0200 Source: cl-screen-sbcl Binary: cl-screen-sbcl Architecture: source all Version: 1.0-4.1 Distribution: unstable Urgency: low Maintainer: Amaya Rodrigo <amaya(a)debian.org> Changed-By: Amaya Rodrigo Sastre <amaya(a)debian.org> Description: cl-screen-sbcl - SLang interface for Steel Bank Common Lisp Closes: 436641 460444 Changes: cl-screen-sbcl (1.0-4.1) unstable; urgency=low . * Non-maintainer upload. * Fix typo in Description (Closes: #460444). - Added a lintian override for this. See: http://lists.debian.org/debian-devel/2008/01/msg00442.html * Downgrade Recommends to Suggests as it's not possible to add an arch-dependent recommends on an arch-independent package, but it is a Lenny release goal to not Recommend unsatisfiable packages (Closes: #436641). Files: 7d761211c76381f65965de0dc867ad99 629 devel optional cl-screen-sbcl_1.0-4.1.dsc 6f39a55ec91b98befa2ca037dabb56a7 3627 devel optional cl-screen-sbcl_1.0-4.1.diff.gz ff622cc229a08acee8ca0a32af1d4fb9 75114 devel optional cl-screen-sbcl_1.0-4.1_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iEYEARECAAYFAkfwBOEACgkQNFDtUT/MKpA9QQCeIcI6ArtzZ+qyKssxnZQI3guL 1ZgAn0Voq5llbuWqFziZReJbpdqd7stj =cfme -----END PGP SIGNATURE----- Accepted: cl-screen-sbcl_1.0-4.1.diff.gz to pool/main/c/cl-screen-sbcl/cl-screen-sbcl_1.0-4.1.diff.gz cl-screen-sbcl_1.0-4.1.dsc to pool/main/c/cl-screen-sbcl/cl-screen-sbcl_1.0-4.1.dsc cl-screen-sbcl_1.0-4.1_all.deb to pool/main/c/cl-screen-sbcl/cl-screen-sbcl_1.0-4.1_all.deb

1 0

[cl-debian] Bug#474483: cl-swank: SWANK-BACKEND:WHO-SETS not implementated
by Ross Boylan 06 Apr '08

06 Apr '08

Package: cl-swank Version: 1:20080223-2 Severity: normal Running emacs 22.1, slime 1:20080223-2 , and sbcl 1:0.9.16.0-1, when I position on a function (actually, macro) invocation and ask for setters (slime | cross-references | who sets) I get the following exception: SWANK-BACKEND:WHO-SETS not implementated [Condition of type SIMPLE-ERROR] Restarts: 0: [ABORT] Return to SLIME's top level. 1: [TERMINATE-THREAD] Terminate this thread (#<THREAD "worker" {BE256E9}>) Backtrace: 0: (SWANK-BACKEND:WHO-SETS MATCH) 1: (SWANK:XREF :SETS "match") 2: (SB-INT:EVAL-IN-LEXENV (SWANK:XREF (QUOTE :SETS) (QUOTE "match")) #<NULL-LEXENV>) 3: ((LAMBDA NIL)) 4: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA NIL) {BE2722D}>) 5: ((LAMBDA NIL)) 6: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> #<FUNCTION (LAMBDA NIL) {AA27905}>) 7: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {B5159D9}> #<CLOSURE (LAMBDA NIL) {BE270C5}>) 8: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {B5159D9}> #<FUNCTION (LAMBDA NIL) {AA27905}>) 9: (SWANK::HANDLE-REQUEST #<SWANK::CONNECTION {B5159D9}>) 10: (SWANK::CALL-WITH-BINDINGS NIL #<CLOSURE (LAMBDA NIL) {BE270A5}>) 11: ((LAMBDA NIL)) 12: ("foreign function: call_into_lisp") 13: ("foreign function: funcall0") 14: ("foreign function: new_thread_trampoline") 15: ("foreign function: #xB7FA94FB") I have no idea if the real source of the problem lies in slime, sbcl, or elsewhere. Please reassign as appropriate. I was trying to go to the definition. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-6-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cl-swank depends on: ii common-lisp-controller 6.12 Common Lisp source and compiler ma cl-swank recommends no packages. -- no debconf information

1 0

[cl-debian] [ann] [objective-cl-announce] Objective-CL 0.2.1
by Matthias Benkard 04 Apr '08

04 Apr '08

Hi all, I have released Objective-CL 0.2.1. This release adds convenience and robustness to the previous one. * Quick Summary Super calls are supported. Bugs have been fixed. You may omit DEFINE-OBJECTIVE-C-GENERIC-FUNCTION calls. * What's New? ** Super Calls Up to now, there was no way of doing the equivalent of a message send to `super' as in Objective-C. This has changed. Just as with CALL-NEXT-METHOD for standard methods, you may now either call (SUPER) as-is or with the arguments you wish to pass to it. See the SUPER function in the reference manual for details. ** Implicit Definition of Objective-C Generic Functions DEFINE-OBJECTIVE-C-METHOD now takes care of defining a suitable OBJECTIVE-C-GENERIC-FUNCTION for you if you don't do so yourself. ** Bug Fixes Lots of little bugs are gone as well. Among others, returning values from Objective-C methods now works much more reliably, and Lisp wrapper objects don't just vanish when the GC runs as long as the corresponding foreign instance is still referenced by Objective-C code. I'm still wondering what to do on garbage-collected Objective-C runtimes. Have fun! ~ Matthias _______________________________________________ objective-cl-announce mailing list objective-cl-announce(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/objective-cl-announce _______________________________________________ announcements site list announcements(a)common-lisp.net http://common-lisp.net/mailman/listinfo/announcements

1 0

[cl-debian] [ann] [objective-cl-announce] Objective-CL 0.2.0
by Matthias Benkard 04 Apr '08

04 Apr '08

Hi all, Objective-CL 0.2.0 has been released. This release is a major milestone on the way to 1.0.0. * Quick summary We can now define Objective-C classes and methods without writing a single line of Objective-C code. The API may not be stable and there might be crashes, but living dangerously is half the fun, right? ;) * What's new? ** Method call syntax #.(enable-method-syntax) We now support Clozure CL's new method call syntax via reader macros. That means you can write: (let ((lock (#/new (find-objc-class 'ns-lock)))) (#/lock lock) (print (#/stringWithCString:encoding: (find-objc-class 'ns-string) "Hi there!" 0)) (#/unlock lock)) In fact, as the reader macro does no more than offer an alternate syntax for symbols, you can do things like using it with APPLY as well: (apply #'#/stringWithUTF8String: (find-objc-class 'ns-string) (list "Hi again.")) ** Class definition You can now define classes. For example, the following will define a subclass of NSObject called MLKMyClass, including a native slot called FOOS and a foreign slot (that is, an Objective-C ivar) called FOO-COUNT (fooCount on the Objective-C side): (define-objective-c-class ns::mlk-my-class (ns::ns-object) ((foos :initargs :foos) (foo-count :foreign-type :int))) Simple CFFI type specifiers are recognised by :FOREIGN-TYPE, but please note that complex types such as struct and union types are not yet supported. ** Method definition You can now define Objective-C methods from Lisp for your own classes. The following will define the Objective-C method -(int)foo:(int)bar:(id)stuff:(id)do:(NSNumber *) on MLKMyClass instances: (define-objective-c-generic-function #/foo:bar:stuff:do: (self y z a b)) (define-objective-c-method #/foo:bar:stuff:do: :int ((self ns::mlk-my-class) (y :int) z a (b ns::ns-number)) (format t "Hello! Z and A are ~A and~&~A, respectively. Have a nice day." z a) (+ y 20)) Usage example: OBJECTIVE-CL> (invoke (invoke (find-objc-class 'mlk-my-class) 'new) :foo 3 :bar "abc" :stuff 3 :do 33) Hello! Z and A are #<NS:GSC-BUFFER-STRING `abc' {8230318}> and #<NS:GS-CACHED-INT `3' {812C5D0}>, respectively. Have a nice day. 23 Note that, at present, you absolutely have to call DEFINE-OBJECTIVE-C-GENERIC-FUNCTION before defining methods, because otherwise you're going to get the wrong type of generic function. All modifiers of the standard method combination should be supported in principle, but it's unlikey they'll work as expected. This is planned for a future release. &REST and &KEY arguments are not supported. #.(disable-method-syntax) ** Struct wrappers When an Objective-C method returns a struct, it is now wrapped in a FOREIGN-STRUCT; likewise for unions. If you want to prevent its automatic deallocation, you need to set its FOREIGN-VALUE-LISP-MANAGED-P property to false. This change has been made because it would otherwise not be safe to discard return values of Objective-C methods, a safety which both Objective-C and Lisp programmers have come to expect. ** COLLECT-CLASSES The new function COLLECT-CLASSES may be used to make all classes known to the Objective-C runtime available as CLOS classes under the NS namespace. In an ideal world, we'd do this automatically at system load-time, but registering such a large number of classes along with their metaclasses takes a long time on some CL implementations (CMUCL, SBCL), so it's the user's decision whether to use FIND-OBJC-CLASS for each class or COLLECT-CLASSES once for now. If you try the release out, please tell me what works and what doesn't. If you can't even get it to compile, that is helpful information as well. Of course, above all, have lots of fun! ~ Matthias _______________________________________________ objective-cl-announce mailing list objective-cl-announce(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/objective-cl-announce _______________________________________________ announcements site list announcements(a)common-lisp.net http://common-lisp.net/mailman/listinfo/announcements

1 0

[cl-debian] Bug#470447: cmucl: FTBFS: make[1]: *** [all] Error 133
by Peter Van Eynde 02 Apr '08

02 Apr '08

Hi, On a real i386 rebuilding cmucl works. So I'm a bit confused as to why you see the problem. My guess is that the reason is that you are building on an AMD64 machine. Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson|

2 1