[Chicken-users] dbus:send bug
Hello, There seems to be an error in dbus:send in the dbus egg. As a test case, the first example given in the dbus egg docs will show the problem: http://wiki.call-cc.org/eggref/4/dbus#examples-you-can-test-with-qt I built the two programs 'car-example-client' and 'car-example-server'. There is a trivial bug in the code for the server; you just need to rename the symbol 'dbus:enable-polling-thread' to 'dbus:enable-polling-thread!'. I used dbus-monitor to inspect the dbus traffic in the test. That program outputs a lot of information, so to keep the following listing short, I've snipped out stuff that is irrelevant to this test. === BEGIN LISTING === $ dbus-monitor [SNIP] $ ./car-example-server [SNIP] $ ./car-example-client [SNIP] signal sender=:1.110 - dest=(null destination) serial=2 path=/Car; interface=com.trolltech.Examples.CarInterface; member=turnRight [SNIP] $ dbus-send --dest=com.trolltech.CarExample /Car com.trolltech.Examples.CarInterface.turnRight [SNIP] signal sender=:1.111 - dest=com.trolltech.CarExample serial=2 path=/Car; interface=com.trolltech.Examples.CarInterface; member=turnRight [SNIP] car is turning to the right === END LISTING === Notice that when I ran car-example-client, the 'dest' field of the dbus message is (null) destination, and the car did not turn to the right, but when I sent a message with dbus-send, with the correct 'dest', car-example-server received and responded to the message. Looking at the definition of dbus:send in dbus.scm, the problem appears to be related to the fact that the function binds the variable 'service' to the correct value, but never uses it. Thank you, -- John Foerch ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] New salmonella directory layout
Hi, The directory layout for salmonella results and feeds has changed to accommodate reports for multiple branches, OS platforms and hardware architectures. Now we have the following URI format: http://tests.call-cc.org/branch/os/arch//mm/dd Example: http://tests.call-cc.org/master/linux/x86/2011/03/15 Christian Kellermann has been running salmonella on OpenBSD/x86, experimental branch. Results for this combination can be found at http://tests.call-cc.org/experimental/openbsd/x86/ The atom feeds location has also changed: http://tests.call-cc.org/feeds/branch/os/arch Example: http://tests.call-cc.org/feeds/master/linux/x86 If you have a custom feed (http://bugs.call-cc.org/browser/salmonella-custom-feeds), they can be found at http://tests.call-cc.org/feeds/branch/os/arch/custom If you want to run salmonella on a different combination of branch, OS platform and hardware architecture and publish your results at tests.call-cc.org, please contact me. Best wishes. Mario -- http://parenteses.org/mario ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] New salmonella directory layout
From: Mario Domenech Goulart mario.goul...@gmail.com Subject: [Chicken-users] New salmonella directory layout Date: Tue, 15 Mar 2011 06:46:36 -0400 Hi, The directory layout for salmonella results and feeds has changed to accommodate reports for multiple branches, OS platforms and hardware architectures. Now we have the following URI format: http://tests.call-cc.org/branch/os/arch//mm/dd Example: http://tests.call-cc.org/master/linux/x86/2011/03/15 Christian Kellermann has been running salmonella on OpenBSD/x86, experimental branch. Results for this combination can be found at http://tests.call-cc.org/experimental/openbsd/x86/ The atom feeds location has also changed: http://tests.call-cc.org/feeds/branch/os/arch Example: http://tests.call-cc.org/feeds/master/linux/x86 If you have a custom feed (http://bugs.call-cc.org/browser/salmonella-custom-feeds), they can be found at http://tests.call-cc.org/feeds/branch/os/arch/custom If you want to run salmonella on a different combination of branch, OS platform and hardware architecture and publish your results at tests.call-cc.org, please contact me. Awesome, Mario! cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Re: dbus:send bug
John J Foerch jjfoe...@earthlink.net writes: There seems to be an error in dbus:send in the dbus egg. As a test case, the first example given in the dbus egg docs will show the problem: http://wiki.call-cc.org/eggref/4/dbus#examples-you-can-test-with-qt On further research, it seems that the bulk of the problem is that dbus:send is entirely mis-documented. That is, it doesn't do what the documentation and examples say it does, but what it does do is still a necessary and useful feature for the bindings to provide. Here is a fairly thorough list of what is wrong with the documentation, so hopefully we can use this to fix it up: Goals and Status * send signals (messages) This is misleading. Signals are a type of message, but not all messages are signals. DBus in General * signal: ... A reply is not necessarily required. This sentence should be omitted or changed. Signals are one-way, period. Some of those would seem to be optional, because the total namespace ends up much deeper than e.g. a URL. However not enough testing has been done to confirm that if you leave out the service and the interface, for example, you won't miss them. Interfaces are optional for both methods and signals. Services are required for methods, but not used at all for signals. Exported functions * dbus:send : send a message, and don't bother waiting for the response. This is misleading. It should say send a signal instead of message. The second clause is also misleading, because there is simply no response to wait for. Then the examples just need to be fixed up to use dbus:call instead of dbus:send. The second example uses dbus:send-and-await-reply, which isn't even part of the api. It seems to have a different call form from dbus:call, so we would have to examine that more closely and figure out what the intent was. Thanks, -- John Foerch ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Issue loading a specifc file with Chicken-Slime
Hi, I have been working through SICP and so am pretty new to Scheme, Chicken, Emacs and Slime. I'm using Chicken 4.6.0, the slime egg (at version 1.0 I believe) and a version of slime itself checked out from CVS on 2011-02-24. It's been working great for me and I've been using C-c C-l to load files without any issue. Just now I copied and pasted some additional code from http://mitpress.mit.edu/sicp/code/ch2.scm into an existing file that was working OK. My resulting file is here: http://paste.lisp.org/display/120550 If I run csi on the command line then (load thatfilefromthepaste.scm) works fine. If I use C-c C-l within chicken-slime to do the same then I do not immediately see an error but nor do I see the t in the message buffer that I normally do. If I switch to the repl and try to invoke anything that was defined in the file I see a message like this: '; pipelined request... (swank:listener-eval ca'. If I switch to the *inferior-lisp* buffer I see the following: Error: (apply) call of non-procedure: () Call history: eval[apply-generic] (map type-tag args) eval[type-tag] (pair? datum) eval[type-tag] (number? datum) eval[apply-generic] (get op type-tags) eval[get] (hash-table-ref/default *op-table* (list op type) (quote ())) eval[get] (list op type) eval[apply-generic] (apply proc (map contents args)) eval[apply-generic] (map contents args) eval[contents] (pair? datum) eval[contents] (number? datum)-- Any ideas? Issues with the code aside I would expect the same behaviour from (load ..) in csi as I would from C-c C-l in slime. Thanks, Conor ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
