Xotcl June 2012

xotcl@alice.wu.ac.at

5 participants
6 discussions

Announcement: Next Scripting Framework 2.0b3 available
by Gustaf Neumann 10 Jun '13

10 Jun '13

Dear Community, We are pleased to announce the availability of the Next Scripting Framework 2.0b3 which can be obtained from http://next-scripting.org Best regards - Gustaf Neumann - Stefan Sobernig =============================================== Announcing NSF 2.0b3 ************************* Major changes relative to NSF 2.0b2 are: * Additional Features: - object parameters: call method "assign" on slot objects, when it is provided - include "-returns" in introspection for aliases and scripted methods. New subcommand "info method returns" for nx. - better compatibility with XOTcl 1.*: * invocation of objects via method interface follows per default the XOTcl 1.* conventions. In order to obtain the semantics of ensemble objects, the object properties "keepcallerself" and "perobjectdispatch" have to be used. * better handling of XOTcl 1.* configure commands (starting with a "-") when list property is lost (Many thanks to Zoran Vasjljevic for the good example) * use different version numbers in serializer to avoid mixups between XOTcl 1 and XOTcl 2 when both packages are installed * Improved Code Quality: - improved performance * rewrite of alias handling (alias reform) * improved branch prediction * significant speedup for handling large numbers of subclasses (subclass reform), avoid repetitious computations * significant speedup on mass-destroy (e.g. on thread exit) - provide better protection for deletion/overwriting of base classes - fixed potential duplicates on diamond inheritance - fixed unknown handling for "-local" and "-system" dispatches - improved compatibility for windows compilations (c89, __WIN32__) - fixed potential crashes * during method caching * error messages * implicit deletions - follow Tcl convention on error messages (start always with lower case) - better handling of multiple errors in a single command. - return GMT dates in Httpd as RFCs require * Improved documentation - fixed typos, improve wordings * Extended regression tests MORE INFO General and more detailed information about the Next Scripting Framework and its components can be found at http://next-scripting.org

2 1

Attributes bug?
by Kurt Stoll 25 Jun '12

25 Jun '12

This looks wrong to me, but I could be wrong - maybe there are prohibitions somewhere that would tell me not to do this. If I define an Attribute "list", and then use the Tcl list command within the assign (and, presumably, other procs of the attribute as well), the attribute's unknown handler is called reflecting an odd invocation. I would suspect that other "overloading" (this is not really overloading, but looks similar so I have used that term; I apologize it that confuses you) of Tcl commands as Attributes would result in similar problems. First, here is a simple Test class without overloading the list command to demonstrate the expected behavior. Note that I redefine unknown so that I can verify the order of the invocation: (Warning - I submitted a question with embedded test code some years ago and this caused problems for people when they attempted to copy-and-paste the code. I don't recall exactly what caused the issue, but I am still using the same email client, so this may have similar issues.) Class create Test1 -slots { Attribute create alist -proc assign { obj var val } { puts "list <$obj> <$var> <$val>" $obj set $var [list $obj $var $val] } -proc unknown { val obj var args } { puts "unknown: $obj $var $val $args" } } > ## Create a test object t1 > Test1 create t1 ::t1 > ## Call alist setter > t1 alist 3 list <::t1> <alist> <3> ::t1 alist 3 > ## Check to see that alist variable set properly > t1 set alist ::t1 alist 3 > ## Force a call to unknown; note that the printed output matches the invocation order > t1 alist this should call unknown unknown: ::t1 alist this should call unknown Now, I create a simple variant. All I have changed is the name of the Attribute from "alist" to "list". But, in this case, when attempting to call the setter, unknown is called (I have done other experiments that showed that it is called when "list $obj $var $val" is called). Also, note that the invocation of unknown is a bit strange; it appears that unknown is directly invoked on the original call (in this case, "t2 list 3"), instead of having the arguments swapped as demonstrated above: Class create Test2 -slots { Attribute create list -proc assign { obj var val } { puts "list <$obj> <$var> <$val>" $obj set $var [list $obj $var $val] } -proc unknown { val obj var args } { puts "unknown: $obj $var $val $args" } } > ## Create a test object t2 > Test2 create t2 ::t2 > ## Call list setter. Unknown handler is called. > t2 list 3 list <::t2> <list> <3> unknown: list 3 ::t2 > ## See what ended up in the list variable. > t2 set list > ## Blank above Am I wrong to expect Test2 (and t2) to behave just as Test1 / t1 behaved? It's not a serious issue for me; I'll just avoid overloading Tcl commands in this context. But, it was unexpected enough for me that I thought it was warranted for me to ask the experts. -Kurt Stoll

2 2

Workaround for "value of parameter could be non-positional argument"
by Arthur Schreiber 21 Jun '12

21 Jun '12

Hello Gustaf, what is the recommended way to work around the warning that is put out by code like this: nx::Class create Test { :property value:required } set value "-h" Test new -value $value # => Warning: value '-h' of parameter '-expected' could be a non-positional argument during: # ::nsf::__#0l configure -expected -h Kind regards, Arthur

2 1

Loading XOTcl crashes
by Kurt Stoll 13 Jun '12

13 Jun '12

(I realize that this is probably not an XOTcl issue, but a ActiveState Komodo issue; however, I have not been able to find an answer through ActiveState, so I may have better luck here.) Running on a Mac, using OSX V10.7.4. I cannot get XOTcl to load properly with ActiveState Komodo V7. I do not have any problem with V6 of that tool. Also, loading XOTcl into tclsh when invoked from the Terminal works. All three environments (Komodo V7, V6, and Terminal / tclsh) are using the same version of Tcl (8.5) and the same version of XOTcl (1.6.6 - I know, down rev by one release). All three versions point to the same library file: /System/Library/Tcl/8.5/xotcl1.6.6/libxotcl1.6.6.dylib. Yet, when I attempt to load XOTcl (using package require XOTcl) from Komodo V7, it gets stuck in an infinite loop: Error in predefined code too many nested evaluations (infinite loop?) while executing "DbgNub_infoCmd exists DbgNub(returnState)" (procedure "catch" line 11) invoked from within "catch {set savedErrorInfo $::errorInfo}" (procedure "::unknown" line 18) invoked from within ... "proc ::xotcl::myproc {args} {linsert $args 0 [::xotcl::self]}" too many nested evaluations (infinite loop?) I don't believe I have changed any relevant settings. Any clues? Thanks, Kurt Stoll

3 4

XOTcl 2 problem
by Kulcsár Ferenc 10 Jun '12

10 Jun '12

Dear list, I'm playing with the example codes placed here: http://next-scripting.org/xowiki/getstart but the XOTcl example isn't working as expected. I have the following error: ./tclsh8.5 proba1.tcl ::g: unable to dispatch method 'parameter' during '::g.parameter' ::g ::xotcl::Object->residualargs ::Greeter ::xotcl::Class->create invoked from within "Greeter create g -parameter Anna" (file "proba1.tcl" line 13) the code in the proba1.tcl file is: package require XOTcl xotcl::Class create Greeter -parameter name Greeter instproc say_hello {} { my instvar name puts "Welcome $name!" } Greeter instproc say_bye {} { my instvar name puts "Goodbye $name!" } Greeter create g -parameter Anna g say_hello The nx version is working well. Any hints are appreciated. TIA, feri P.s.: The nsf2.0b3 and git versions display the same error. -- Kulcsár Ferenc <crusader(a)netbsd.hu>

2 1

Segfault after undefining "new" proc in a class namespace
by Arthur Schreiber 08 Jun '12

08 Jun '12

Hey Gustaf, The following is propably a very uncommon use case, but it causes a segfault, so I think it's rather serious: % package require nx % nx::Class create A {} % proc ::A::new {} { return "something" } % A new something % rename ::A::new "" % A new [1] 2515 segmentation fault (core dumped) tclsh Kind regards, Arthur

2 2

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 2012