Xotcl

xotcl@alice.wu.ac.at

2 participants
653 discussions

performance
by Kristoffer Lawson 13 Feb '01

13 Feb '01

Just for interest I implemented one of the OO tests from Doug's shootout (http://www.bagley.org/~doug/shootout/) in XOTcl to see how it would fare. Specifically it was the method call speed test (http://www.bagley.org/~doug/shootout/bench/methcall/). I have attached my code to this email. According to my own tests, it didn't do terribly well, but it's difficult to say whether this is a limitation of Tcl (which doesn't do very well in several of those speed tests) or just a sign that there might be some room for optimisation in XOTcl itself. Now what would be interesting would be a comparison with iTcl -- but as I don't know it I'll leave that for someone else. Any comments? - ---------- = = ---------//--+ | / Kristoffer Lawson | www.fishpool.fi|.com +-> | setok(a)fishpool.com | - - --+------ |-- Fishpool Creations Ltd - / | +-------- = - - - = --------- /~setok/

2 1

XOTcl based HTML generation
by Kristoffer Lawson 13 Feb '01

13 Feb '01

A friend here at Fishpool made a simple HTML generation library in XOTcl which does automatic indentation and generally makes code that deals with HTML much neater. Currently it's all based around a HtmlDocument class, which can be used to build a whole document or parts of a document (which can then be added to other HtmlDocuments). Naturally this can be extended with for things like tables, forms and whatever, although it already includes methods for some of those. I'm sure it might make the xodoc source code a lot cleaner (and I've been tempted to stick it in there when editing it) :-) If anyone is interested, do check it out: http://dev.fishpool.fi/oss/htmllib/ - ---------- = = ---------//--+ | / Kristoffer Lawson | www.fishpool.fi|.com +-> | setok(a)fishpool.com | - - --+------ |-- Fishpool Creations Ltd - / | +-------- = - - - = --------- /~setok/

1 0

some xodoc fixes
by Kristoffer Lawson 13 Feb '01

13 Feb '01

I'm not sure if I should send this to Uwe and Gustaf directly or this list, so if this is wasting bandwidth then tell me and I'll try to remember to send further suggested updates directly to them. Anyhow here are some changes I made: - It bugged when a file did not end with a newline (this was actually the cause of my earlier problem). - Slightly changed the errorCode documentation section. - Fixed some other HTML bugs (quite possibly caused by my previoues ventures into playing with xodoc ;-). - Removed a lot of space that was being fed out. This was problematic when I use the <pre> tags. The downside is that the code looks rather messy, but I might just be posting a kind of solution for that soon. Anyhow, my version of the xodoc file is attached here. - ---------- = = ---------//--+ | / Kristoffer Lawson | www.fishpool.fi|.com +-> | setok(a)fishpool.com | - - --+------ |-- Fishpool Creations Ltd - / | +-------- = - - - = --------- /~setok/

1 0

Abstract method f args called
by Catherine Letondal 12 Feb '01

12 Feb '01

Hi, Say I have the following class hierarchy: Class C0 C0 instproc f args { puts "(C0) I am [self] class [[self] info class] in method [self proc]" } Class C1 -superclass C0 C1 abstract instproc f args Class C2 -superclass C1 C2 instproc f args { puts "(C1) I am [self] class [[self] info class] in method [self proc]" next } So, the method f is: - defined at the top of the hierarchy - abstract in the middle of the hierarchy. - redefined at the bottom When I run: C2 c2 c2 f I get: (C1) I am ::c2 class ::C2 in method f Abstract method f args called and I cannot reach the top method? Is this on purpose? -- Catherine Letondal -- Pasteur Institute Computing Center

2 1

document operation
by Kristoffer Lawson 09 Feb '01

09 Feb '01

Am I right in assuming that currently xodoc doesn't generate documentation for classes within namespaces, if these classes aren't exported from the namespace? Normally this would be correct (I think I suggested it myself), but when another exported class is a sub-class of the non-exported one the user of the exported class still needs to see the non-exported one (to check method definitions etc.). So for this situation documentation should still be generated. Would this work in xodoc? Maybe the non-exported one would be marked somehow so as the reader knows that the class is not meant for direct use. - ---------- = = ---------//--+ | / Kristoffer Lawson | www.fishpool.fi|.com +-> | setok(a)fishpool.com | - - --+------ |-- Fishpool Creations Ltd - / | +-------- = - - - = --------- /~setok/

1 0

Annoucing new init+destroy scheme
by Uwe Zdun 07 Feb '01

07 Feb '01

Dear XOTcl Community, Annoucing new init+destroy scheme: Due to constant questions and problems regarding object destroy + creation + recreate, we have decided to provide a new destroy scheme in XOTcl 0.84. It will have only slight observable differences to the current destroy scheme, but is more flexible and allows for recreation. I'll explain how it is currently implemented: "create" and "alloc" are both now Class instprocs handling creation for their instances. I.e. [self] alloc is wrong ... correct is now: <className> alloc [self] There is a new method "instdestroy" on Class that handles physical destruction of an object. The method "destroy" on Object has now the behavior: Object instproc destroy args { [[self] info class] instdestroy [self] } Everything is written in C ... I'll use XOTcl code just for explanation... "create" now distinguishes between: 1) creating a new object: calls alloc + <doInitializations> 2) recreating an existing object calls: [self] class <givenClass> [self] cleanup ;# resets <self> into a state as after original <init> <givenClass> recreate [self] "recreate" is a new method that can be customized. Its default behaviour is: <doInitializations> <doInitializations> is called in C and is the same for recreate and (1): - search for parameter default values - call "-" initialization methods - call "init" each of those will have a method call that can be changed, intercepted, etc. Of course, you can also overload or intercept cleanup, recreate, instdestroy, etc. Comments? Greetings, Uwe -- Uwe Zdun Specification of Software Systems, University of Essen Phone: +49 201 81 00 332, Fax: +49 201 81 00 398 zdun(a)xotcl.org, uwe.zdun(a)uni-essen.de

1 0

Widgets
by Rick Hedin 06 Feb '01

06 Feb '01

Hello all. I want to build an object on top of a canvas. The object adds some internationalized features. I'm not clear how to manage the XOTcl object in conjunction with the Tk object. For now, I'm just managing the two as separate entities. Icanvas icanvas .f ;# I pass the path for the tk object. pack .f.icanvas -fill both -expand true ;# And manipulate the tk object with tk commands. Or maybe I should: pack [icanvas tkpath] -fill both -expand true Or give my object a truly wicked name: Icanvas .f.icanvas ;# Will this work? Or wrap every tk command in my xotcl object. What is your thinking regarding widgets from XOTcl? Regards, Rick

4 7

Widgets
by Rick Hedin 06 Feb '01

06 Feb '01

Thanks for the interesting responses. So people are: 1) Using a broker to associate Tk objects and XOTcl objects. 2) Using a filter to intercept Tk commands. 3) Wrapping a Tk object in an XOTcl object. Maybe some day we can integrate the Tk object commands with the XOTcl object commands. I would like to help, but if I do it, I won't get to it for years. (The part of the project that would need that functionality is that far off.) Regards, Rick

1 0

Probable bug: no method calls with "next" & init
by Kristoffer Lawson 06 Feb '01

06 Feb '01

[~] Class Foo [~] Foo instproc init {arg} { puts "arg: $arg" } [~] Foo instproc whatever {system} { puts "sys: $system" } [~] Class Bar -superclass Foo [~] Bar instproc init {} { next myArg -whatever niceSystem } [~] Bar ob called "next" with too many arguments - ---------- = = ---------//--+ | / Kristoffer Lawson | www.fishpool.fi|.com +-> | setok(a)fishpool.com | - - --+------ |-- Fishpool Creations Ltd - / | +-------- = - - - = --------- /~setok/

3 11

Classes and namespace
by Kristoffer Lawson 30 Jan '01

30 Jan '01

[~] package require XOTcl 0.83 [~] namespace eval Foo { >Class MyClass >MyClass instproc init {} { >AnotherClass newChild >} >Class AnotherClass >} AnotherClass [~] Foo::MyClass new invalid command name "AnotherClass" while evaluating {Foo::MyClass new} Ie. it appears as if methods aren't run in the same namespace as where classes exist (or a child namespace of this). I know this isn't exactly a bug (as I don't think it's specified anywhere?), but I believe the natural behaviour would be for AnotherClass to be found in the example above, as it's specified within the same namespace as Foo. Is the any chance the current behaviour could be altered to one that I think is more intuitive? Or is there a good reason why not? - ---------- = = ---------//--+ | / Kristoffer Lawson | www.fishpool.fi|.com +-> | setok(a)fishpool.com | - - --+------ |-- Fishpool Creations Ltd - / | +-------- = - - - = --------- /~setok/

2 2

← Newer
1
...
58
59
60
61
62
63
64
65
66
Older →

Jump to page:

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