Xotcl June 2008

xotcl@alice.wu.ac.at

5 participants
4 discussions

Announcement: XOTcl 1.6.0 available
by Gustaf Neumann 25 Jun '08

25 Jun '08

Dear XOTcl Community, XOTcl 1.6.1 is available. This release provides in short: - improved orthogonality for introspection, - improvements in the serializer - some minor fixes Starting with XOTcl 1.6.0, release packages for XOTcl are available for Debian GNU/Linux. XOTcl is included in upcoming Ubuntu releases, starting with Ubuntu 8.10 "Interpid Ibex" (see also: http://media.wu-wien.ac.at/download.html). Many thanks to Stefan Sobernig for his help! See below for more details concerning the release Best regards -gustaf neumann Announcing XOTcl 1.6.1 ************************* We are pleased to announce the availability of XOTcl 1.6.1 Major changes relative to 1.6.0 are: * Extended and generalized "info" method * Generalized serializing package: when deserializing code, now consistenly no constructors are called. In previous versions, constuctors were called on slots; due to the point above, this is not needed; background: the previous solution had problems in aolserver ns_eval, when a slot-constructor called db-functions, since during ns_eval, the database handles are non-functional) * Fixes for potential crashes when methods were called with invalid arguments * Improved documentation * Extended regression tests 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

1 0

Re: [Xotcl] Improvement proposal for instfilters and guards
by Stefan Sobernig 05 Jun '08

05 Jun '08

> BTW, have you or somebody else already considered to make an XOTcl > implementation for Jacl (Tcl on Java)? Well, there is a cool piece of (on-going) work which is an amalgam of Tcl/XOTcl + Hecl/Jacl, mastered by Uwe Zdun: see http://frag.sourceforge.net/

3 2

Object eval Problem
by Ben Thomasson 04 Jun '08

04 Jun '08

Hi, I have a problem with the following code: [xotcl-1.6.0]$ ./xotclsh % ::xotcl::Object eval set a 5 5 % ::xotcl::Object eval ::xotcl::Object set a 5 5 % ::xotcl::Object eval ::xotcl::Object set Segmentation fault This line works fine: ::xotcl::Object eval ::xotcl::Object set a 5 This line causes a Segmentation fault: ::xotcl::Object eval ::xotcl::Object set It should just throw an error. This code is similar but does not have the problem: [xotcl-1.6.0]$ ./xotclsh % ::xotcl::Object eval ::xotcl::Object lappend a 5 5 % ::xotcl::Object eval ::xotcl::Object lappend wrong # args: should be "lappend varName ?value value ...?" % exit This was on a fresh compile of Tcl8.4.19 and XOTcl1.6.0. Let me know if you see this in your builds. Thanks, Ben

2 1

Improvement proposal for instfilters and guards
by Eckhard Lehmann 03 Jun '08

03 Jun '08

Hi all, instfilters and -guards are great features in XOTcl. Nevertheless there is room for improvement... In 99% of the cases one (I at least) creates a filter that needs to be triggered only at a certain method. Even if one has several methods to intercept, it is often easier to create separate methods and use guards to trigger them. Guards are great, but the overall picture of the code gets overly complicated in such cases. Therefore I'd like to propose an argument "-methods" to the filter command, that tells the filter to only be triggered on execution of the methods in the corresponding list: Class A ... A instproc do1 {} ... A instproc do2 {} ... A instproc do3 {} ... A instproc do1Filter {} ... # trigger only at do1 A instfilter do1Filter -methods do1 ;# or -methods {do1 do3} # rather than A instfilter do1Filter A instfilterguard do1 {[string eq [self calledproc] do1]} Is such a feature already planned? If not, is there anything that speaks against it? -- Eckhard

2 4

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 June 2008