Xotcl

xotcl@alice.wu.ac.at

2 participants
653 discussions

XOTcl 1.4.0 available
by Gustaf Neumann 18 Feb '06

18 Feb '06

Fellow xotclers, i am glad to annouce the availablity of xotcl 1.4.0. The major changes against 1.3.9 are: * Improved Functionality * new option: ::xotcl::configure softrecreate on|off if softrecreate is set, class relations (superclass, subclass, class, instances) are not affected by a recreate; this allows files with class definitions more easily to reload + easier syntax for providing commands for initializing default values + setting and querying options for ::xotcl::configure simiar to set * Improved Code Quality: + fixed a bug in connection with nonpositional arguments and "args" + fixed a bug with adding on the fly transitive mixin classes + fixed a bug with filter states after next + fixed omitted error message after calling self with unknown subcommands + fixed a bug with variable traces on thread exit (triggered by volatile) + fixed incorrect rpm dependencies + cleaner compile for xotcl for gcc 4.* under linux + don't destroy namespace imported child objects + info children returns true children, not namespace imported objects/classes + unsetting the global variable "cmd" from predefined.xotcl + Upgraded TEA to 3.5 + more regression tests addeed For more details about the changes, please consult the ChangeLog and documentation on www.xotcl.org. The window binaries will follow soon. all the best -gustaf neumann

1 0

instprocs in C
by Aamer Akhter 18 Feb '06

18 Feb '06

Critcl allows us to easily create tcl callable C procs. Is there something similar avaliable for xotcl? Is there any C api documentation? -- Aamer Akhter / aakhter(a)gmail.com

4 5

Non-pos arguments with args
by Kurt Stoll 17 Feb '06

17 Feb '06

I am having difficulty getting non-positional arguments to behave correctly with args. The simple example below shows what I have found. This does not appear to be appropriate behavior. Am I doing something wrong? Object obj obj proc pr1 { {-npos default} args } { puts "npos: $npos" puts "args: $args" } > ## This works: > obj pr1 a npos: default args: a > > ## As does this: > obj pr1 -npos 3 a npos: 3 args: a > > ## But this does not: > obj pr1 -npos 3 npos: 3 args: -npos 3 > > ## I expected args to be {}, but instead it contains the non-positional parameter Thanks for any insight you can provide. -Kurt Stoll

2 1

Re: [Xotcl] Object destruction on exit
by Kristoffer Lawson 04 Feb '06

04 Feb '06

On 3 Feb 2006, at 17:11, Gustaf Neumann wrote: > Kristoffer Lawson schrieb: > >> >> Well this generally happens automatically anyway. If they are >> resources for which this does not happen, can we be sure that this >> is what the programmer wants? > > consitency is important. > in oo-systems, the programmer has a "contract" with the system, > that for every object > the life-cycle starts with the constructor and ends for the > destructors. > This is simlar to finalize() in java. > normally, you do not want to distinguish btwn. "manual" and > "automatic" destroys (which happen > btw. in various situations). I would say this depends very much on your point of view. In systems with prevalent persistence then the existence of an object continues until it is explicitly destroyed. Ie. automatic destruction does not occur. You can few objects in two different ways, as in-memory entities they exist only as long as the application exists. But you can also take the view that the in-memory entities are just representations of the actual object, which resides also on disc. > You cound do e.g. > > ::xotcl::Object setExitHandler {set ::xotcl::onEXIT 1} > > and check this variable from the destroy method whether or not the > db-instance > should be deleted. Yes, this could be one possible way round that. / http://www.fishpool.com/~setok/

1 0

Ordering of Children
by Matthew Dodwell 03 Feb '06

03 Feb '06

Hi, Hopefully a simple question. I'm building a tree view controller and am seeing an unexpected ordering issue. I add with; MemoryLineController instproc init {} { my AddNode "File Diagnostics" my AddNode "Real time Diagnostics" my AddNode "Graphs" my AddNode "Post-Processing" } MemoryLineController instproc CreateTreeview {} { set counter 1 foreach childNode [my info children *gNode*] { $childNode BuildTreeNode [my tree] $counter incr counter } } MemoryLineController instproc AddNode {name} { eval GUINode [self]::[my autoname gNode%02d] -DisplayName {$name} } So the init method adds my root level nodes The order I get out is; Post-Processing File Diagnostics Real time Diagnostics Graphs i.e. the last is displayed first and then the next 3 in order. Why is this and what is the best way to correct it? thanks Matthew

2 2

Object destruction on exit
by Kristoffer Lawson 03 Feb '06

03 Feb '06

When XOTcl exits, it seems that the [destroy] method is called on all objects. The first question is whether this is wise .. possibly. The problem is I would like to build a transparent layer for persistence storage which could be applied to a wide range of applications. The problem naturally is that the objects in the persistence storage get destroyed when the application exits :-) / http://www.fishpool.com/~setok/

4 4

frappr page
by Gustaf Neumann 29 Jan '06

29 Jan '06

Hi everybody, maybe you are interested in joining the frappr group of xotcl to locate the people based on the google map... See: http://www.frappr.com/xotcl best regards -gustaf neumann

2 2

global variable "cmd"
by Koen Danckaert 06 Jan '06

06 Jan '06

Hello, The predefined.xotcl file uses a global variable "cmd": foreach cmd {array append lappend trace eval} ... Which may, of course, give unexpected results: tclsh % set cmd mycommand mycommand % package require XOTcl 1.3.8 % set cmd eval Regards, Koen

2 1

RE: [Xotcl] Weird behaviour
by Murr, Florian 05 Jan '06

05 Jan '06

Thanks a lot! While trying to understand your suggestions, I further simplified my own code and found the problem. It was all my fault! In the slave interpreter 'Celsius2Kelvin' is an unknown proc and therefor a room-object with this name gets created and I got confused. - I definitly have to get some rest soon :-) Sorry for having bothered you and thanks for your suggestions! - Florian -----Original Message----- From: Gustaf Neumann [mailto:neumann@wu-wien.ac.at] Sent: Thursday, January 05, 2006 3:13 PM To: Murr, Florian Cc: xotcl(a)alice.wu-wien.ac.at Subject: Re: [Xotcl] Weird behaviour i am somewhat confused be the code (why are you creating and deleting interpreters?) is the following code doing, what you are trying? (aggregates rooms on floors with a simple syntax) -gustaf =================================================== package require XOTcl namespace import -force ::xotcl::* namespace eval tih { Class Floor \ -instproc has cmds {eval $cmds} Class Room -superclass Class \ -parameter {{count 0} currTemp} \ -instproc new args { set name "[self callingobject]::[namespace tail [self]]-[my incr count]" eval [self] create $name $args } Room room -parameter {{currTemp 300}} Room guestRoom -superclass room Room bathRoom -superclass room Room guestBathRoom -superclass bathRoom proc Celsius2Kelvin {a} { expr {$a+273.15} } Floor floor3 -has { guestRoom new guestBathRoom new -currTemp [Celsius2Kelvin 30] } puts "rooms on floor 3: [floor3 info children]" foreach c [floor3 info children] { puts "temperature in room $c is [$c currTemp]" } } exit

1 0

Weird behaviour
by Murr, Florian 05 Jan '06

05 Jan '06

I extracted the code below from a very large XOTcl program that I am developing right now. The output of the last line 'puts "uuuuu guest_bathroom3 [guest_bathroom3 currTemp]"' puzzles me! If I uncomment the line 'set temp [Celsius2Kelvin 20]' the output is even weirder (an error message). Any helpful comments? Regards, - Florian My code: package require XOTcl namespace import xotcl::my xotcl::self xotcl::next xotcl::Class xotcl::@ namespace eval tih { Class Floor -parameter { {cubicles {}} } Class Room -parameter { {cubicles {}} } Room instparametercmd currTemp # --- 'unknown'-mechanism. Floor proc createRoom01 {floor aName args} { #set temp [Celsius2Kelvin 20] set room [eval {Room create $aName} $args] $floor lappend cubicles $aName $room set Floor $floor } Floor instproc rooms {{a {}}} { ;# getter/setter my instvar cubicles if {[llength $a]} { set itp [self]_createRoom01 interp create $itp interp alias $itp unknown {} ::tih::Floor createRoom01 [self] set rval [$itp eval $a] interp delete $itp return } set rval [list] foreach i $cubicles { # xxx verbessern! if {[$i istype Room]} { lappend rval $i } } set rval } proc Celsius2Kelvin {a} { expr {$a+273.15} } Floor floor3 -rooms { guest_room guest_bathroom3 -currTemp [Celsius2Kelvin 30] } #puts "uuuuu guest_room [guest_room currTemp]" puts "uuuuu guest_bathroom3 [guest_bathroom3 currTemp]" }

2 1

← Newer
1
...
28
29
30
31
32
33
34
...
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