Xotcl October 2001

xotcl@alice.wu.ac.at

7 participants
9 discussions

What functions from xotcl.c could constitute C-API ?
by Zoran Vasiljevic 31 Oct '01

31 Oct '01

IOW, if I would like to write a C-level extensions to XOTcl (which I desperately need to!) what functions from the xotcl.c file should be taken into consideration ? I know that the public API is (still) not supported but I'd need some solution pretty fast. Any ideas ? Thanks, Zoran Vasiljevic

2 1

0.9.1
by Gustaf Neumann 21 Oct '01

21 Oct '01

Hi folks, i've put 0.9.1 on the server. See below for the changes. We have also new figures from the shootout benchmark, XOTcl is here now about twice as fast as OTcl. I've posted these figures to c.l.t as well. The benchmark results and sources are on the download page (supplemental resources) best regards -gustaf ===================================================== XOTcl methcall: 2.040u 0.010s 0:02.05 100.0% 0+0k 0+0io 283pf+0w objinst: 4.730u 0.030s 0:04.76 100.0% 0+0k 0+0io 283pf+0w OTcl methcall: 4.050u 0.000s 0:04.04 100.2% 0+0k 0+0io 330pf+0w objinst: 9.240u 0.010s 0:09.24 100.1% 0+0k 0+0io 330pf+0w itcl methcall: 3.130u 0.000s 0:03.12 100.3% 0+0k 0+0io 285pf+0w objinst: 6.040u 0.000s 0:06.03 100.1% 0+0k 0+0io 286pf+0w stooop methcall: 6.930u 0.010s 0:06.94 100.0% 0+0k 0+0io 259pf+0w objinst: 14.180u 0.000s 0:14.17 100.0% 0+0k 0+0io 259pf+0w classytcl methcall: 3.030u 0.020s 0:03.04 100.3% 0+0k 0+0io 284pf+0w objinst: 8.980u 0.040s 0:09.02 100.0% 0+0k 0+0io 284pf+0w ==================================================== 2001-10-20 Gustaf.Neumann(a)wu-wien.ac.at * reimplemented method 'new' of Class in C * various cleanups for stub handling * added regression test for stub library 2001-10-18 Uwe Zdun <uwe.zdun(a)uni-essen.de> * removed linking glitch in 0.9: stub enabled lib was linked with non-stub enabled obj-files. * added a stub enabled lib to Windows make procedure * renamed stub enabled lib to (lib)xotcl-tclstubs.(so|dll) 2001-10-17 Uwe Zdun <uwe.zdun(a)uni-essen.de> * removed "can't instvar to link" problem during aliasing to a link var

1 0

RE: xotcl and tclkit
by Theado, Brian P. 19 Oct '01

19 Oct '01

On Fri, 19 Oct 2001 09:07:31 +0200, Gustaf Neumann wrote: > the xotcl binaries are built with tcl 8.3.2. > therefore it should work without compiling only with > 8.3. > however, when it is compiled with 8.4, it will work. I remember that stubs support was recently added to xotcl.

2 1

Fwd: Re: xotcl and tclkit
by Gustaf Neumann 19 Oct '01

19 Oct '01

---------- Forwarded Message ---------- Subject: Re: [Xotcl] xotcl and tclkit Date: Fri, 19 Oct 2001 09:07:31 +0200 From: Gustaf Neumann <neumann(a)wu-wien.ac.at> To: Hal Heisler <hh(a)heisler.net> On Thursday 18 October 2001 23:14, you wrote: > Hello, > > I'd like to use xotcl with tclkit. When I try to load the distributed > linux binary libxotcl.so I see undefined symbol: tclEmptyStringRep > > I have not tried building xotcl myself yet, perhaps that's what I need to > do. Tclkit uses a tcl/tk 8.4 snapshot from cvs. > > Just wondering if anyone's been down this road. the xotcl binaries are built with tcl 8.3.2. therefore it should work without compiling only with 8.3. however, when it is compiled with 8.4, it will work. best regards -gustaf neumann > Thanks, > Hal > _______________________________________________ > Xotcl mailing list - Xotcl(a)alice.wu-wien.ac.at > http://alice.wu-wien.ac.at/mailman/listinfo/xotcl -------------------------------------------------------

2 1

xotcl and tclkit
by Hal Heisler 18 Oct '01

18 Oct '01

Hello, I'd like to use xotcl with tclkit. When I try to load the distributed linux binary libxotcl.so I see undefined symbol: tclEmptyStringRep I have not tried building xotcl myself yet, perhaps that's what I need to do. Tclkit uses a tcl/tk 8.4 snapshot from cvs. Just wondering if anyone's been down this road. Thanks, Hal

1 0

can't instvar to link
by Gustaf Neumann 17 Oct '01

17 Oct '01

Dear XOTcl users, we just found a small glitch in xotcl 0.9, which will happen only in rare situations. However, if you see an error message "can't instvar to link", drop us a short note, and you get immediately a fix. Since the bug appears to be pretty rare, we will wait with the patch release a little. best regards -gustaf neumann

1 0

XOTcl 0.9
by Gustaf Neumann 15 Oct '01

15 Oct '01

Fellow XOTcl community, here comes the annoucemnt of XOTcl 0.9. best regards -gustaf neumann .uwe zdun ================================================================================== Announcing XOTcl 0.9 ******************** WHAT IS XOTCL? XOTcl is an object-oriented extension of Tcl that was derived from OTcl. In short, XOTcl tries to provide a highly flexible, reflective, component-based, and object-oriented environment. It integrates language support for high level concepts which are not found in other languages, with reasonable performance. It prevails the Tcl programming style and the dynamic/introspective nature of the language, rather than introducing other language's styles and rigidness (such as C++) into Tcl. RECENT CHANGES relative to 0.85 are: - new functionality: * Per object filters: in addition to traditional filters (which are called now "instfilters") one can define now filters per objects as well. XOTcl supports now the following interceptors: per class filters and mixins (called instfilters and instmixins), and per object filters and mixins (called filters and mixins). * filterguards: This is a new mechanism to specify when filters should be applied (see tutorial and language reference). * Namespace transparency for XOTcl procs and instprocs: In previous releases, the programmer was responsible to use :: prefixes in order to safely address Tcl commands from XOTcl (e.g. an instance of a class defining "set" had to use ::set). Now, the namespaces of Classes and objects are ignored for command resolutions avoiding potential interferences. * Namespace on demand: XOTcl objects allocate namespaces on demand (e.g. when procs or child objects are defined). * XOTcl is now a "well behaved" extension: When libxotcl is loaded everything resides in the ::xotcl namespace. Use "namespace import xotcl::*" to import the global commands (xotclsh and xowish do this per default). * Improved parameter settings (see tutorial) - Speed improvements: * Significant speedup through the more consequent use of Tcl_Objs for accessing classes and objects. * Methods for append/lappend/array etc. are about 3 times faster through the use of insttclcmd (see below) * Parameter methods: Methods for accessing parameters are now 4 to 5 times faster. In the following example, "name" and "age" are parameters: Class Person -parameter {{age 0} name} Person p1 -age 99 -name gustaf puts [p1 age] setting and retrieving of parameters has now roughly the same speed as the set methods - Reduced memory consumption for objects and classes: The size of XOTclObject structure went from 172 bytes to 48 bytes by * allocating assertion structures and namespaces on demand, and * by and by omitting in the default setup metadata 10 thousand XOTcl objects consume now on a 32bit machine about 2 MB of memory in total (including whatever Tcl needs for commands etc) - new Class methods * instparametercmd: define a new getter/setter for instance variables for instances of used class * insttclcmd: evaluate an Tcl command in the context of an object - new Object methods: * parametercmd: define a new getter/setter for instance variables for an object * configure: method to call a series of methods on an object e.g. Object o1 o1 configure -set x 1 -set y 2 - new subcommands for info method: * info methods: returns procs, commands and mixins, accepts modifiers: -noprocs, -nocmds, -nomixins * info instfilters * info filter accepts new modifiers: -guards, -order - fixes: * propagation of return codes (e.g. ... return -code continue ...) which is needed for Tk event maps * various actiweb fixes (agent migration was broken) * improved documentation - Support for AOLserver: XOTcl is now prepared for use in the AOL-server. The stubs for AOL-server are integrated in XOTcl (many thanks to Zoran Vasiljevic). The required patch for the AOL-Server is available from http://media.wu-wien.ac.at/download.html#aol - Stub-library support: XOTcl supports now the stub library. This means that it is less dependent on particular Tcl implementations. The support was quite tricky since some commands used by XOTcl (like Tcl_IncrObjCmd, Tcl_UpvarObjCmd, ...) are not exported by the stub library, and the solution has to work in the multithreaded AOL-server environment) - potential incompatibilities: * "[self] next" is gone, use "next" instead. * The access of instance variables through the tcl-set command is deprecated and works only when the namespace is created. Instead of Object o set o::x 1 use Object o o set x 1 * procsearch returns a different format (see Changelog) 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

announce - XOTclIDE Version 0.20
by Artur Trzewik 13 Oct '01

13 Oct '01

Hi The new version 0.20 of XotclIDE Integrated Interactive Developing Envirorment for Xotcl is ready. The most important changes in version 0.19 and 0.20 - Full featured configuration browser. For managing sets of versioned components - Changes Browser. To see the changes among different component versions (something like diff) - Version System Browser. To see the components without the need to load them. - Error Reporting Tool - to allow user to send tcl error stack as XML file - Method Call Tracker - to track the method calls. - Many user friendly GUI additions Download, Documantation, Screenshoots http://www.xdobry.de/xotclIDE/ Artur Trzewik

1 0

generating error stacks messages from xotcl
by Artur Trzewik 10 Oct '01

10 Oct '01

Hallo For XotclIDE I have built a Error Stack browser witch can parse error messages (in errorInfo) a convert it to methods list. I have following problem. Consider the example Class TestA TestA instproc fooA {} { [self] fooC } TestA instproc fooB {} { fooC } TestA instproc fooC {} { error {error from fooC} } TestA a a fooA generate following errorInfo error from fooC while executing "error {error hier}" (procedure "fooC" line 2) ::sample0 ::TestA->fooC invoked from within "[self] fooC" (procedure "fooA" line 2) ::sample0 ::TestA->fooA invoked from within a fooB # generate following message error from fooC while executing "error {error hier}" (procedure "fooC" line 2) invoked from within "fooC" (procedure "fooB" line 2) ::sample0 ::TestA->fooB invoked from within I the first example we have the lines (procedure "fooC" line 2) ::sample0 ::TestA->fooC This can be good used for parsing errorInfo I the second there are only (procedure "fooC" line 2) The same bahavior is by method chains with "next" or filter methods. Can the xotcl be changed for same dubug infos? Artur Trzewik

2 1

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 October 2001