Hullo -
I'm afraid I found a bug that will generate an "unable to dispatch" error if the argument list & body of an instproc are both empty. You will notice that as long as either contain something, it's ok. Notice the body of "Bar notpuke", it's just a single comment. See the code below:
Gustaf -- This is the build that I downloaded from you on October 18th at: http://media.wu-wien.ac.at/download/xotcl-1.3.3.tar.gz
-- blah.tcl -- package require XOTcl 1.3
namespace import ::xotcl::* Class Foo Foo instproc puke {} {}
Class Bar Bar instproc notpuke {} {#}
Class Ack Ack instproc notpuke {a} {}
Bar b b notpuke
Ack a a notpuke x
Foo f f puke
-- End -- Produces the following error: ::f: unable to dispatch method 'puke' while executing "f puke" (file "/homes/bschofie/blah.tcl" line 20)
-----Original Message----- From: xotcl-bounces@alice.wu-wien.ac.at [mailto:xotcl-bounces@alice.wu-wien.ac.at]On Behalf Of Gustaf Neumann Sent: Friday, October 15, 2004 1:03 PM To: xotcl@alice.wu-wien.ac.at Subject: Re: [Xotcl] xotcllib?
On Friday 15 October 2004 18:47, Schofield, Bryan (GE Transportation) wrote:
Does xotcllib, or some other collection of XOTcl utility
packages exist? just the library that comes with the source in xotcl*/library -gustaf
-- Univ.Prof. Dr.Gustaf Neumann Abteilung für Wirtschaftsinformatik und Neue Medien Wirtschaftsuniversität Wien, Augasse 2-6, 1090 Wien _______________________________________________ Xotcl mailing list Xotcl@alice.wu-wien.ac.at http://alice.wu-wien.ac.at/mailman/listinfo/xotcl
Dear Bryan,
I'm afraid I found a bug that will generate an "unable to dispatch" error
if the argument list & body of an >instproc are both empty. You will notice that as long as either contain something, it's ok. Notice the body of >"Bar notpuke", it's just a single comment. See the code below:
we have a behavior in xotcl that we inherited from otcl: when instproc is invoked with an empty argument list and an empty body, this instproc is deleted. Most probably, we should do the following: a) produce an error, when someone tries to delete a non.existing proc/instproc b) document this behavior somewhere more visible.
-gustaf