Xotcl November 2004

xotcl@alice.wu.ac.at

6 participants
17 discussions

Filters on classes
by MichaelL＠frogware.com 15 Nov '04

15 Nov '04

I'm using XOTcl 1.3.1. This code: Object instproc someFilter {args} { puts "self class = [self class]" puts "self called class = [self calledclass]" puts "self = [self]" puts "self calledproc = [self calledproc]" puts "args = $args" puts "" next } Class TestA -parameter {{x 0}} TestA filter someFilter TestA a a x a x 10 produces this output: self class = ::xotcl::Object self called class = self = ::TestA self calledproc = a args = self class = ::xotcl::Object self called class = ::xotcl::Class self = ::TestA self calledproc = unknown args = a self class = ::xotcl::Object self called class = ::xotcl::Class self = ::TestA self calledproc = create args = a self class = ::xotcl::Object self called class = ::xotcl::Class self = ::TestA self calledproc = alloc args = a invalid command name "a" Note that filtering on "TestA a" seems to prevent the creation of an obj named "a". Any ideas?

1 0

RE: Non-positional args with no value cause core dump
by Schofield, Bryan (GE Transportation) 11 Nov '04

11 Nov '04

I found another problem with non-position args... an argument of "--" can cause a core dump. Consider the following. Object o o proc foo {{-a A}} {b} { puts "$a $b" } o foo "B" #--> "A B" o foo "-" #--> "A -" o foo "---" #--> "A ---" o foo "--" #--> core dump. > -----Original Message----- > From: Schofield, Bryan (GE Transportation) > Sent: Wednesday, November 10, 2004 9:17 AM > To: xotcl(a)alice.wu-wien.ac.at > Subject: Bug: Non-positional args with no value cause core dump > > > Gustaf/Uwe - > > I found a little bug in 1.3.3 that I downloaded on October > 15th from=20 > http://media.wu-wien.ac.at/download/xotcl-1.3.3.tar.gz > > The following causes a core dump on my Solaris workstation: > > Object o > o proc foo {{-foo 1}} {} { > puts "foo: $foo" > } > > o foo > #--> "foo: 1" > > o foo -foo 0 > #--> "foo: 0" > > o foo -foo > #--> BOOM! > > > > Just thought I'd pass that on. Regards > -- bryan >

1 0

Bug: Non-positional args with no value cause core dump
by Schofield, Bryan (GE Transportation) 10 Nov '04

10 Nov '04

Gustaf/Uwe - I found a little bug in 1.3.3 that I downloaded on October 15th from=20 http://media.wu-wien.ac.at/download/xotcl-1.3.3.tar.gz The following causes a core dump on my Solaris workstation: Object o o proc foo {{-foo 1}} {} { puts "foo: $foo" } o foo #--> "foo: 1" o foo -foo 0 #--> "foo: 0" o foo -foo #--> BOOM! Just thought I'd pass that on. Regards -- bryan

1 0

XOTcl extending nonPosArgs class
by Giovanni Cristelli 04 Nov '04

04 Nov '04

With version 1.3.0 I've tried to extend the class to support a new option in using the following code: xotcl::nonPosArgs proc in { allowedValues argName args} { if { [lsearch $allowedValues $args] == -1 } { error "Invalid value |$args| for option $argName (allowed values: [join $allowedValues {, }])" } } example: Class create A A proc y {{{-q:in {add remove}} add}} {} { puts $q } A y; # prints add A t -q bad; # throw an error A y -q remove; # prints remove With version 1.3.1 this code doesn't work anymore and the error returned is: ::xotcl::nonPosArgs: unable to dispatch method 'in {add remove}' How can I change the prototype to make it work again ? Thanks, Giovanni. -------------------------------------------------------------------- CONFIDENTIALITY NOTICE This message and its attachments are addressed solely to the persons above and may contain confidential information. If you have received the message in error, be informed that any use of the content hereof is prohibited. Please return it immediately to the sender and delete the message. Should you have any questions, please contact us by replying to webmaster(a)telecomitalia.it. Thank you www.telecomitalia.it --------------------------------------------------------------------

1 0

RE: [Xotcl] [Fwd: Bug with namespace'd Class?]
by Schofield, Bryan (GE Transportation) 02 Nov '04

02 Nov '04

I don't think it is a bug, and I don't think it is unexpected behavior...exactly; more on that in a second. In fact, if it *were* available, as you expected, I'd consider that bad behavior since no package should ever export commands into the root namespace automatically. So, if it's not behaving badly, but still isn't exactly what you expected, where does this discrepancy come from, and how is it resolved? I suggest that documentation is culprit and the solution. I think that an "XOTcl & Namespaces" section or a "General XOTcl Usage" section that describe this situation would beneficial. Btw, I remember when I first stumbled across this; it made me step back and scratch my head too. --bryan > -----Original Message----- > From: xotcl-bounces(a)alice.wu-wien.ac.at > [mailto:xotcl-bounces@alice.wu-wien.ac.at]On Behalf Of Damon Courtney > Sent: Tuesday, November 02, 2004 3:27 PM > To: xotcl(a)alice.wu-wien.ac.at > Subject: RE: [Xotcl] [Fwd: Bug with namespace'd Class?] > > > I figured as much. I guess I'll just do import the > commands into the > root namespace. It doesn't really bother me, but some of the other > Tcl'ers are real sticklers about namespacing everything. I just use > what's best. 0-] > > So, does this still constitute a bug then, or should I > just chalk it > up to expected behavior? > > Thanks, > > Damon > > > because "self" is a command in the xotcl namespace. you > will also find > > that there are others, such a "my" > > > > If you don't import xotcl, you end up with source that > looks like this: > > > > ::xotcl::Class foo > > Foo instproc bar {} { > > puts "[::xotcl::self] is a [::xotcl::my info class]" > > } > > > > > > I'd suggest, do something like the following... > > > > package require XOTcl 1.3 > > namespace eval fooPackage { > > namespace import ::xotcl::* > > Class Foo > > Foo instproc bar {} { > > puts "[self] is a [my info class]" > > } > > } > > > > > > hope that helps. > > -- bryan > > > >> -----Original Message----- > >> From: xotcl-bounces(a)alice.wu-wien.ac.at > >> [mailto:xotcl-bounces@alice.wu-wien.ac.at]On Behalf Of > Damon Courtney > >> Sent: Tuesday, November 02, 2004 2:23 PM > >> To: xotcl(a)alice.wu-wien.ac.at > >> Subject: [Xotcl] [Fwd: Bug with namespace'd Class?] > >> > >> > >> Why does this not work? > >> > >> package require XOTcl > >> > >> ::xotcl::Class Foo > >> > >> Foo instproc bar {} { > >> puts "SELF = [self]" > >> } > >> > >> Foo foo > >> % Foo foo > >> ::foo > >> % foo bar > >> invalid command name "self" > >> > >> > >> But, if I "namespace import ::xotcl::*" and make the > >> class with just > >> the Class command (not ::xotcl::Class), it works. > >> > >> Any ideas? > >> > >> D > >> > >> PS: Windows, Tcl 8.4.3, XOTcl 1.3.1 > >> > >> _______________________________________________ > >> Xotcl mailing list > >> Xotcl(a)alice.wu-wien.ac.at > >> http://alice.wu-wien.ac.at/mailman/listinfo/xotcl > >> > > > > _______________________________________________ > > Xotcl mailing list > > Xotcl(a)alice.wu-wien.ac.at > > http://alice.wu-wien.ac.at/mailman/listinfo/xotcl > > > > > _______________________________________________ > Xotcl mailing list > Xotcl(a)alice.wu-wien.ac.at > http://alice.wu-wien.ac.at/mailman/listinfo/xotcl >

1 0

RE: [Xotcl] [Fwd: Bug with namespace'd Class?]
by Schofield, Bryan (GE Transportation) 02 Nov '04

02 Nov '04

because "self" is a command in the xotcl namespace. you will also find that there are others, such a "my" If you don't import xotcl, you end up with source that looks like this: ::xotcl::Class foo Foo instproc bar {} { puts "[::xotcl::self] is a [::xotcl::my info class]" } I'd suggest, do something like the following... package require XOTcl 1.3 namespace eval fooPackage { namespace import ::xotcl::* Class Foo Foo instproc bar {} { puts "[self] is a [my info class]" } } hope that helps. -- bryan > -----Original Message----- > From: xotcl-bounces(a)alice.wu-wien.ac.at > [mailto:xotcl-bounces@alice.wu-wien.ac.at]On Behalf Of Damon Courtney > Sent: Tuesday, November 02, 2004 2:23 PM > To: xotcl(a)alice.wu-wien.ac.at > Subject: [Xotcl] [Fwd: Bug with namespace'd Class?] > > > Why does this not work? > > package require XOTcl > > ::xotcl::Class Foo > > Foo instproc bar {} { > puts "SELF = [self]" > } > > Foo foo > % Foo foo > ::foo > % foo bar > invalid command name "self" > > > But, if I "namespace import ::xotcl::*" and make the > class with just > the Class command (not ::xotcl::Class), it works. > > Any ideas? > > D > > PS: Windows, Tcl 8.4.3, XOTcl 1.3.1 > > _______________________________________________ > Xotcl mailing list > Xotcl(a)alice.wu-wien.ac.at > http://alice.wu-wien.ac.at/mailman/listinfo/xotcl >

2 1

[Fwd: Bug with namespace'd Class?]
by Damon Courtney 02 Nov '04

02 Nov '04

Why does this not work? package require XOTcl ::xotcl::Class Foo Foo instproc bar {} { puts "SELF = [self]" } Foo foo % Foo foo ::foo % foo bar invalid command name "self" But, if I "namespace import ::xotcl::*" and make the class with just the Class command (not ::xotcl::Class), it works. Any ideas? D PS: Windows, Tcl 8.4.3, XOTcl 1.3.1

1 0

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 November 2004