Xotcl September 2010

xotcl@alice.wu.ac.at

4 participants
4 discussions

XOTcl 1.6.6 available
by Gustaf Neumann 03 Nov '11

03 Nov '11

Announcing XOTcl 1.6.6 ************************* Dear XOTcl Community, We are pleased to announce the availability of XOTcl 1.6.6 Major changes relative to 1.6.5 are: * improved 64-bit compatibility (expat) * fixed minor memory leaks (info methods, forward error case) * fixed potential cyclic dependencies via namespace imports during cleanup * fixed potential crash with var-traces being fired twice * compatibility with Tcl 8.6b1 * fix for debian packaging For more details about the changes, please consult the ChangeLog and documentation. The planned next release will be 2.0.0 MORE INFORMATION General and more detailed information about XOTcl and its components can be found at http://www.xotcl.org best regards -gustaf neumann

1 1

new feature idea
by vitick＠gmail.com 01 Oct '10

01 Oct '10

It occurred to me that XOTcl could benefit or it's "coolness" value could be raised even more if it had method chaining similar to JQuery. Example: Class create Myclass Myclass :method a args { process {*}$args; } Myclass :method b args { process {*}$args; } Myclass create myobj execute: myobj :chain :a :b {value1 value2} or: myobj :chain :a :b :a :b :destroy {value1 value2} ################ syntax: obj :chain :method1 :method2 .... {arg1 arg2 ...} ################ functionality: each method would be executed in the order listed with the args provided in the end of the "chain" method. ################ This functionality is even more enhanced with mixins and superclasses where each chained method would be passed to a mixin/superclass via [next]. P.S. this is not really a feature request at the moment because I see you are very busy doing a lot of work on Next. And that has more priority. Also, the "chain" functionality can be easily done via scripting it myself. Again, for the "coolness" or "extra power" value, it would be nice to have that, in my opinion, as a built-in feature.

3 2

Bug in filter processing?
by Kristoffer Lawson 30 Sep '10

30 Sep '10

Take a look at this code: package require XOTcl 1.6 namespace import xotcl::* Class Foo Foo instproc hello {} { puts hello } Foo instproc myfilter {args} { puts "\nme: [self]" ::set targetclass [my info class] puts "targetclass: $targetclass" puts "calledproc: [self calledproc]" ::set r [next] puts "back from next" puts "paramcmds: [$targetclass info instparametercmd]" } Foo instfilter myfilter Foo ob ob hello ob foo So first I have a filter installed which does nothing but print some information, and checks something using the [info] method afterwards. I call an instantiated object with [hello] (an existing method) and again with [foo] (a non-existing method). The latter is when things get interesting. Check the output: me: ::ob targetclass: ::Foo calledproc: configure back from next paramcmds: me: ::ob targetclass: ::Foo calledproc: init back from next paramcmds: me: ::ob targetclass: ::Foo calledproc: hello hello back from next paramcmds: me: ::ob targetclass: ::Foo calledproc: foo back from next me: ::alloc ::alloc: unable to dispatch method 'info' while executing "my info class" (procedure "cleanup" line 4) ::alloc ::Foo->myfilter ::Foo ::xotcl::Class->recreate ::Foo ::xotcl::Class->create ::Foo ::xotcl::Class->unknown ::Foo ::xotcl::Class->create ::Foo ::xotcl::Class->unknown ::Foo ::xotcl::Class->create ::Foo ::xotcl::Class->unknown invoked from within "$targetclass info instparametercmd" (procedure "foo" line 9) ::ob ::Foo->myfilter invoked from within "ob foo" (file "filtertest.tcl" line 24) me: ::alloc targetclass: ::Foo calledproc: destroy back from next paramcmds: me: ::info targetclass: ::Foo calledproc: destroy back from next paramcmds: me: ::ob targetclass: ::Foo calledproc: destroy back from next paramcmds: ... So while the [hello] method works as expected, things get totally weird for [foo]. The first thing we notice is that it doesn't jump out at [next] (which should give an error as it does not exist). It continue execution of the filter after [next]. This may or may not be intended, I don't know. The documentation is not clear on this. More interesting still, we end up with a totally unexpected error. The thing I believe is happening is that, for some reason or other [$targetclass info instparametercmd] is not ending up calling [info] for $targetClass, but creating an object called ::info (and thus overriding the original Tcl command). How [alloc] gets involved in the filter chain too, I am not sure. My guess is that the "unknown method" that resulted from [foo] is being interpreted by the XOTcl $targetclass C implementation as an error that occurred there, and that a new instance called "info" or possibly "alloc" should be created. This causes major havoc as soon as an unknown method is called. Does the filter code look correct? This happens with 1.6.2. I had a quick look at CHANGES for later versions and while there was some mention of memory leaks in [info] I wasn't sure if there was anything that would have fixed this. Any ideas? -- Kristoffer Lawson, Co-Founder, Scred // http://www.scred.com/

4 8

Problem with slots and moving objects
by Neil Hampton 28 Sep '10

28 Sep '10

I am having a problem/have found a bug with slots created with an -initcmd. If I set a value on an object containing a slot with an initcmd and then move it an error gets thrown every time I read the value. Class Fred -slots { Attribute a -initcmd { set _ 4 } } Fred x x a 4 x move y y a can't read "a": invalid command name "::x" Are there any simple work arounds for this other than having to write a method for 'a'? Neil Hampton www.rostrvm.com

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

Xotcl September 2010