Xotcl September 2005

xotcl@alice.wu.ac.at

11 participants
8 discussions

Re: [Xotcl] memory leak analysis
by Gustaf Neumann 01 Oct '05

01 Oct '05

-------- Original-Nachricht -------- Betreff: Re: [Xotcl] memory leak analysis Datum: Fri, 30 Sep 2005 19:25:52 +0200 Von: Gustaf Neumann <neumann(a)wu-wien.ac.at> An: Ben Thomasson <ben.thomasson(a)gmail.com> Referenzen: <44eb229c0509300852m10e879a7k(a)mail.gmail.com> Ben Thomasson schrieb: > Hi, > > I am writing a simulation engine using xotcl. I have noticed as I > create and destroy objects over time this process will use all > available memory. I have tracked down and eliminated old objects. what do you mean by "old objects"? > With the object count staying roughly constant the memory continues to > increase at about 1k per second. What tools or tricks are useful for > tracking down memory leaks in Tcl or XOTcl? are you using theads? If something is leaking memory it is most likely more complicated than just object creation and destruction. At least on my system the following script runs without any leaks. for {set i 1} {$i < 10000000} {incr i} { set o [Object create obj-$i] $o destroy } can it be that you are somewhere building a table (assoc. array) with object names? xotcl has a bunch of compile flags to report memory usage, one can compile tcl with a flag that enables a command for memory checking. -gustaf > > Thanks, > > Ben > > -- > You know you have reached perfection of design not when you have > nothing more to add, but when you have nothing more to take away. > --Antoine de Saint Exupéry > >------------------------------------------------------------------------ > >_______________________________________________ >Xotcl mailing list >Xotcl(a)alice.wu-wien.ac.at >http://alice.wu-wien.ac.at/mailman/listinfo/xotcl > >

4 5

Re: [Xotcl] mixin and __unknown in 1.3.7
by Zoran Vasiljevic 30 Sep '05

30 Sep '05

Am 30.09.2005 um 18:26 schrieb Gustaf Neumann: > was this with 1.3.8 already? > > NO! 1.3.8 WORKS! I could just not let go... So SOMETHING did change there... NOTE: I did not change ANYTHING in the ttrace. I just plugged new Serializer class and new 1.3.8 lib into my code. Eh... I think I'm getting to old and tired of all these things... Well, anyway, thanks for your patience and guidance! You saved my day :-) Cheers Zoran

1 0

memory leak analysis
by Ben Thomasson 30 Sep '05

30 Sep '05

Hi, I am writing a simulation engine using xotcl. I have noticed as I create and destroy objects over time this process will use all available memory. I have tracked down and eliminated old objects. With the object count staying roughly constant the memory continues to increase at about 1k per second. What tools or tricks are useful for tracking down memory leaks in Tcl or XOTcl? Thanks, Ben -- You know you have reached perfection of design not when you have nothing more to add, but when you have nothing more to take away. --Antoine de Saint Exupéry

1 0

mixin and __unknown in 1.3.7
by Zoran Vasiljevic 30 Sep '05

30 Sep '05

Hi! Seems like this one is broken :-( Watch: lexxsrv:nscp 1> DbsTree d ::d lexxsrv:nscp 2> d mixin XXXTree expected a class as mixin but got XXXTree lexxsrv:nscp 3> d mixin XXXTree lexxsrv:nscp 3> The first time it broke, the second time it did. All of the classes are loaded on demand by the __unknown mechanism. If I hoever do this: lexxsrv:nscp 1> XXXTree ::XXXTree lexxsrv:nscp 2> DbsTree d ::d lexxsrv:nscp 3> d mixin XXXTree all is fine. I do not know when this crept in since we are still using the 1.1 for our production server. I'm now starting to move all to 1.3 and, peng! Please help! Zoran

1 0

xotcl 1.3.7 problem
by Koen Danckaert 29 Sep '05

29 Sep '05

Hello, There seems to be a problem with instvar alias names in xotcl 1.3.7 Consider the following code: Class C -parameter {number name} C instproc test {} { my instvar {number x} name puts "$name $x" } C c -name koen -number 25 c test This fails with can't read "name": no such variable It works when the aliased variables are put last in the instvar command: my instvar name {number x} Regards, Koen Danckaert

2 1

TIP #257: Object Orientation for Tcl
by Jeff Hobbs 29 Sep '05

29 Sep '05

I know that many on this list will be interested in the following TIP just propsed: TIP #257: Object Orientation for Tcl http://www.tcl.tk/cgi-bin/tct/tip/257 This is indeed based on xotcl, but it is *not* xotcl. There are good reasons for this overall (but not necessarily for each individual change ;) ). I would like xotcl users who are interested to please read this TIP carefully, but to bear a few items in mind: 1. We know that syntax will change. Some is terminology, and not all features are being adopted. This is not intended to be a TIP to include all of xotcl, but rather to provide a well featured oo:: base. itcl, snit and whatever isn't included from xotcl should be easily built on this base. At the same time, xotcl as an independent code base will continue to work just fine. 2. Not all Tcl users are OO lovers. Some are just OO agnostic and want to remain that way (like all the non-CS technical folks). For those who like OO, most come from OO worlds dominated by Java. Terminology that they will be familiar with is important. At the same time, we want to create the best system for Tcl (and Tcl is better than Java). The oo::tcl approach at least tries to address this without losing many of the benefits of XoTcl. 3. Megawidget support - whatever the solution it absolutely must be consistent with the goals of bringing a standard megawidget facility to Tk. I personally use snit::widget for this, with its delegation based system. I have not seen any other system come close to its ease of megawidget development (including xotcl based ones). Many of the large systems in Tcl are Tk-based, and they will benefit greatly from standardized OO. However, if the system isn't "Tk friendly", it will be rejected. I'm sure there are lots of other good, pithy comments I could make, but I'll let you guys (and gals) digest the basics first. Regards, Jeff Hobbs, The Tcl Guy http://www.ActiveState.com/, a division of Sophos

8 19

XOTcl 1.3.7 available
by Gustaf Neumann 28 Sep '05

28 Sep '05

Dear XOTcl community, I am pleased to annouce XOTcl 1.3.7. Major changes relative to 1.3.6 are: * Improved Functionality + new option "switch" for non positional arguments to be used to toggle the default value. A switch is a non positional argument without extra argument. + new option "isnextcall" for self + new command "::xotcl::configure filter on|off" to turn off filters. needed for serializing objects/classes with active filters + several improvements for serializer to handle e.g. application methods on Object/Class (needed for ad_instproc in oacs) + improving namespace resolving in for object/class references + moving all library packages into namespaces + preventing "new" from overwriting objects + allow xotcl to be used in slave interpreters * Improved code quality: + fixed namespace confusion in forward to expression calling xotcl methods + fixed possible crash in instvar when empty variable names are used + some code cleanup + improved documentation * new method "method" for defining methods (experimental): Instead of using e.g. Object o1 Class C o proc m1 {} {....} C instproc m2 {} {....} C proc m3 {} {....} one can use now o method m1 {} {....} C method m2 {} {....} C method -per-object m3 {} {....} in general, we can support options for method definitions, which can be used as well for mixins, filters or info (instead of the "inst" prefix). This way the problem of finding appropriate names for distinguishing between object or class matters can be solved, in rather rare cases (when referring the to class object) "-per-object" can be used. The according name changes will happen in xotcl 2.0. For more details about the changes, please consult the ChangeLog and documentation. MORE INFO General and more detailed information about XOTcl and its components can be found at http://www.xotcl.org Best regards, Gustaf Neumann Uwe Zdun

1 0

Re: XOTcl is great!!
by Gustaf Neumann 09 Sep '05

09 Sep '05

Taral schrieb: > Hello, > > I recently came across XOTcl and found it very very useful. I am > working on optimizing some legacy compiler code which is written in > TCL. I would like to make it object-oritented and so I started using > XOTcl. So far I have found aouut 90% reduction in execution time. > Overall I'm getting great performance by using XOTcl. wow, this is an impressive number; good to hear that. > I would like to Thank You guys for writing such a great library. > > Of course I have couple of questions for you. I will really appreciate > it if you can help me here. > > (1) Is there any way to all the objects or instances based on > parameter value? For example, I would like to request object names of > all objects where given parameter's value is equal to 5. There is no built-in support for this. a straigthforward approach is the following which might be sufficient in many situations: =========== # define method expr for all Objects, the operands are taken from # the instance variables Object instforward expr -objscope # define method select with some abitrary tcl expression. All objects, # for which the expression returns 1 are returned Class instproc select {expr} { set result_list [list] foreach o [my allinstances] { if {![catch {$o expr $expr} result]} { puts "$o expr {$expr} -> $result" if {$result} { lappend result_list $o } } } return $result_list } =========== so, now we define a view classes and objects with some instance variables Class C -parameter {{x 10}} Class D -superclass C C c1 C c2 -x 11 D d1 -x 100 D d2 D d3 d3 unset x finally, we try it out with some demo queries foreach q { {$x > 10} {$x >= 10} {$x < 1} {[string match *00* $x]} } { puts "C select $q --> {[lsort [C select $q]]}\n" } Note that in this example, all instances of C are checked for the expression, if you use "... [Object select {$x > 10}]", all objects will be checked. This approach might be good enough for small examples and medium speed requirements. If you have larger number of objects, and you cant restrict the query to smaller classes, you should try to build an index based on associative arrays, which could replace the "allinstances" in the code above. > (2) Do you have more example code pieces? I would like to see more > sample implementation to help me with the syntax. I'm also learning > TCL language at the same time using XOTcl :) i am sure, you have seen the tutorial and the examples in xotcl*/apps and xotcl*/library. There are a few more on: http://mini.net/tcl/XOTcl http://wiki.tcl.tk/references/10971! > (3) Is there any way to represent relationship across two classes? For > example, Class A is related to Class B with one-to-many relationship. a few class/class relations and object/class relations are maintained by xotcl (e.g. superclass, class, mixins). A start point might be ::xotcl::Relations, which is used to implement a uniform interface to mixins (and instmixins ...), which allows to specify "... mixin add ...", # "... mixin delete ...", "... mixin set ...", etc. In principle, the same interface could be used for application level relations as well... In current applications, the classes use and maintain a list of related object/classes. Often, it is conveniant to use aggregations to express 1:1 or 1:n relationships. > (4) If there is a way to define relationship, is it possible to query > objects of classes in the relationship? For example, I would like to > get all the objects of Class B related to given object of Class A > (like a1) across given one-to-many relationship. In this case result > would be list of object handles of Class B that matches based on given > primary key (identifier) value between class A and B. a good key identifier is the object name. see the following snipplet, how such behavior could be obtained. We define class A, which maintains the relationship to some other objects. if an instances exists that relates e.g. to object c1, we could check there some properties with expr like above... Class A -parameter {relates_to} A a1 A a2 a1 set relates_to {c1 c2} foreach o [A allinstances] { catch { if {[lsearch -exact [$o relates_to] c2] > -1} { puts "could check $o" } } } hope theses examples help a little. -gustaf PS: when i was writing this mail i saw that the classtack information within methods called via the method "expr" is not correct. It will be fixed in the next release.... > > Please provide some guidance to implement above functionality using XOTcl. > > Thanks a lot in advance. > > May be in future I would like to contribute to XOTcl. I wish to be in > touch with you guys. > > Regards, > Taral

4 9

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 2005