Xotcl

xotcl@alice.wu.ac.at

2 participants
653 discussions

RE: [Xotcl] Is this a bug?
by Murr, Florian 13 Dec '05

13 Dec '05

Thanks a lot for your thorough explanation! I tend to think in "invariants" and I memorized that having a method specialized this way C instproc someMethod {args} { next } should leave my program invariant with respect to functionality. But this obviously has the exception of getter/setter methods. Regards, - Florian -----Original Message----- From: Gustaf Neumann [mailto:neumann@wu-wien.ac.at] Sent: Thursday, December 08, 2005 4:15 PM To: Murr, Florian Cc: xotcl(a)alice.wu-wien.ac.at Subject: Re: [Xotcl] Is this a bug? Murr, Florian schrieb: >Yes, you are right, I overload the setter/getter method and expected >naively that it just prints the puts-statement and works otherwise >unchanged. [Should have read the manual more properly, I guess :-)] > > for each parameter a method for getting and setting variables registered. This method is a "instparametercmd" implemented in C, which is very similar to the set method. This can be as well explained with the forwarder, which could be used to implement the *parametercmds Class C C instforward x %self set %proc now a method named x is defined, that calls "[self] set x" when issued. eg. C c1 c1 x 123 here "c1 set x 123" is called, or in the following line "c1 set x" is issued. puts [c1 x] This behavior is more or less identical to Class C C instparametercmd x or to Class C -parameter x therefore, the instparamtercmd is strictly speaking not needed, but predates instforward and is slightly faster, since everything is in C. The parameters do more, since they can be used to provide as well default values which are used during initialization of objects. anyhow, in all cases a method named "x" is defined. When you define an instproc named x Class C C instproc x args {...} you will overwrite the method "x", in a similar manner as you can overwrite any tcl command, e.g proc if args { ...} Therefore, there is no chance to do a next in these cases, because the class has now the new method (instproc) instead of the c-level implementation we had earlier. Furthermore "next" works only when methods are shadowed, when a same-named method is defined by a class/object earlier in the precedence order. This can be achieved e.g. via mixins or filters. therefore, in your example >X instproc y {args} { > puts "[self] y '$args'" > my instvar y > if {[llength $args]} { set y [lindex $args 0] } > next >} > > the "next" is not doing anything useful, you should replace the last line of your instproc by e.g. "return $y", such that .... [x1 y] ... works hope this explains, how this works... -gustaf neumann

2 1

XOTcl 1.3.9 available
by Gustaf Neumann 09 Dec '05

09 Dec '05

Dear XOTcl community, I am pleased to annouce the availability of XOTcl 1.3.9. Major changes relative to 1.3.8 are: * Improved Functionality + new subcommand for self: [self args] return the full argument list of the current call + "<obj> info vars" does not trigger read traces on each variable anymore + Serializer: exportMethods accepts forwards/instforwards now as well + new switch -nocomplain for "mixin|instmixin|filter|instfilter delete" to avoid error messages when deleting entries not there (similar unset) + require automatically a namespace when a childobject is added + new command ::xotcl::__qualify: convert an relative name into an command name (exactly as create does it, ignoring namespaces from transparent interceptors) * Improved code quality: + fixing version numbers for package require + Upgraded TEA to 3.4 + updated rpm build (many thanks to Ildiko Schmidt and Alexander Bergolth) + fixed bug with error propagation when getter/setter methods are used for parameters (many thanks to Manfred Stelzhammer for pointing this out) 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 Best regards, Gustaf Neumann Uwe Zdun

1 0

RE: [Xotcl] Is this a bug?
by Murr, Florian 08 Dec '05

08 Dec '05

When I run the script, I get: ::x y 'y0' ::x y 'y1' ::x init '' ::x y '' expected 'y1', but got: '' Yes, you are right, I overload the setter/getter method and expected naively that it just prints the puts-statement and works otherwise unchanged. [Should have read the manual more properly, I guess :-)] I can achieve my desired result too, by doing something like: X instproc y {args} { puts "[self] y '$args'" my instvar y if {[llength $args]} { set y [lindex $args 0] } next } But I wanted to have an 'official' answer to this behaviour. Regards, - Florian -----Original Message----- From: Gustaf Neumann [mailto:neumann@wu-wien.ac.at] Sent: Thursday, December 08, 2005 12:43 PM To: Murr, Florian Cc: xotcl(a)alice.wu-wien.ac.at Subject: Re: [Xotcl] Is this a bug? Hmm, are you sure? the script you have sent does not produce the message you are indicating.... ~/scripts> set ::xotcl::version 1.3 ~/scripts> set ::xotcl::patchlevel .8 ~/scripts> Class X -parameter { > {y y0} >} ::X ~/scripts> X instproc init {args} { puts "[self] init '$args'"; next } ~/scripts> X instproc y {args} { > set x [next] > puts "[self] y '$args'" > set x >} ~/scripts> X create x -y y1 ::x y 'y0' ::x y 'y1' ::x init '' ::x ============================= however, most probably it is not doing what you might be expecting. your method y overwrites the setter method of parameter y, therefore in this example, not much happens in the next of method y. maybe you had in mind to overload the setter/getter method, which you can do e.g. with a mixin (see below) Class X -parameter { {y y0} } -instmixin [Class new -instproc y args { puts "[self] [self proc] $args" set x [next] puts "[self] [self proc] $args setter returns <$x>" return $x }] X create x -y y1 puts x.y=[x set y]

2 1

Is this a bug?
by Murr, Florian 08 Dec '05

08 Dec '05

package require XOTcl 1.3.8 namespace import xotcl::* Class X -parameter { {y y0} } X instproc init {args} { puts "[self] init '$args'"; next } X instproc y {args} { set x [next] puts "[self] y '$args'" set x } X create x -y y1 puts "expected 'y1', but got: '[x y]'" regards, - Florian Murr

2 1

Class naming and creation
by Zoran Vasiljevic 22 Nov '05

22 Nov '05

Hi! What I need to do sometimes is to be able to cache classes because their creation (in our case) might be a costly operation. For example: Class HeavyClass set hc [HeavyClass new] $hc whatevermethod can be quite time consuming. What I'd like to do is to "cache" "things" created by "new" or even for: HeavyClass hc hc whatevermethod What would be the best way to achieve this caching? Thanks for help. Zoran

2 3

Problem with initialisation
by Kristoffer Lawson 13 Nov '05

13 Nov '05

This is with XOTcl 1.3.6, but I couldn't find if 1.3.8 fixes it. The following code does not appear to work as expected: package require XOTcl namespace import xotcl::* Class A A instproc init {test} { puts "init: $test" } A instproc foo {text} { puts "foo: $text" } A instproc bar {text} { puts "bar: $text" } A new "on taas" -foo jou -bar blah A new -foo jou -bar blah "on taas" The first will work, but the latter will not. The error is: wrong # args: should be "bar text" ::xotcl::__#1 ::A->bar ::xotcl::__#1 ::xotcl::Object->configure ::A ::xotcl::Class->create ::A ::xotcl::Class->new invoked from within "A new -foo jou -bar blah "on taas"" (file "dashCreateTest.tcl" line 23) / http://www.fishpool.com/~setok/

2 1

Encoding problems with web application
by Erwin Sistinger 31 Oct '05

31 Oct '05

Hello, since 1 year i have had a small xotcl web application running on a server with Redhat Linux (don´t know the version, changed since), xotcl 1.1 (i´m using the actiweb packages), mysql 3.23 and mysqltcl installed on it. A few weeks ago the admin of the server upgraded to a new redhat version and also to mysql 4.1.14. Since then the encoding of the web pages my application delivered was not correct anymore - characters like ü or ä weren´t displayed. I changed the charset-information in the html-header to utf8, converted my old database (which was in iso88591) to utf8 and upgraded to mysqltcl 3.0.1 - still no utf8-characters in the html-pages. I tried to find a solution within the actiweb code but although i found some lines with "encoding" in I it don´t really know what is happening in there - could anybody please give me a small hint? Thanks a lot, Erwin the server´s configuration: Redhat Linux 3.0ES xotcl 1.1 (i´m using the actiweb packages) mysqltcl 3.0.1 mysql 4.1.14 -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner

2 1

Extending nonposArgs in XOTcl
by Shawn Jury 26 Oct '05

26 Oct '05

Hello, I am trying to extend nonposArgs to include more checks and I am having a hard time. I have gotten basic checks working, but I am not able to get some of the more complicated checks working. The tutorial shows that the syntax for extending nonposArgs is: *someobject|someclass* *proc|instproc* methodName {?optional arguments? argName args} { ... } I have not been able to get the ?optional arguments? to work. Example: I am trying to get some checks done that will check for specific values of the Arg. I would like to be able to pass those values into the check. xotcl::nonposArgs proc RANGE {allowedRange argName args} { .....code to verify the range } The syntax to use this would be similar to: Class Foo Foo instproc setMtu {{-mtu:RANGE 54-65535 "1500"}} {} { .... } This is similar to what Giovannni Cristelli asked in the post titled XOTcl extending nonPosArgs class from November 2004. Is there any way to do this currently? I am trying to replace a bloated package that is currently being used which has many of these checks available. I have tried many combinations of syntax to get this to work and have not been able to figure it out. Thanks, Shawn

2 1

Missing -nocomplain in [unset]
by Kristoffer Lawson 23 Oct '05

23 Oct '05

Well, the subject says it all. That Tcl option seems to be missing from the XOTcl equivalent. / http://www.fishpool.com/~setok/

2 1

xotcl 1.3.8 available
by Gustaf Neumann 02 Oct '05

02 Oct '05

Dear XOTcl community, XOTcl 1.3.8 is available. It is essentially a bug-fix release for 1.3.7, containing the bugs detected by Koen, Zoran and Ben fixed. The windows binary will follow tomorrow. best regards -gustaf neumann

1 0

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