Xotcl April 2009

xotcl@alice.wu.ac.at

5 participants
5 discussions

Send NULL arg to Class constructor
by Colin Ross 12 May '09

12 May '09

Hi all I have ported over one of our applications from using itcl to using xotcl. I have a lot of code that already uses the itcl stuff, so the port must be backwards compatible. I have the following issue. Can anyone give me an idea how I can get around it? A script that shows my issue is as follows: #!/usr/bin/tclsh package req XOTcl namespace import ::xotcl::* ::xotcl::Class Connect -parameter { {telnet} {ssh} {ip} } Connect instproc init {node args} { [self] instvar telnet [self] instvar ip } Connect dev node -ip "127.0.0.1" -telnet The above does not work, as it seems that the telnet arg must not be NULL, however, I need this to be NULL, as it is just a flag. If I pass in: Connect dev node -ip "127.0.0.1" -telnet ³² This works, however, this is not backwards compatible with how things were with itcl, and I have too many users/scripts to change how this is done. There are potentially 2 ways around this, however, I am unable to find information on if either of them are possible: 1. Allow the passing in of a NULL argument 2. Prevent the constructor parsing args so that I can parse my own I would appreciate any assistance Cheers Colin

4 5

Re: [Xotcl] XOTcl packages
by Stefan Sobernig 04 Apr '09

04 Apr '09

(sorry for double posting, forgot about digest mode) Jeff, > Message: 2 > Date: Fri, 03 Apr 2009 11:29:34 -0700 > From: Jeff Hobbs <jeffh(a)activestate.com> > Subject: Re: [Xotcl] XOTcl packages > To: Victor Mayevski <vitick(a)gmail.com> > Cc: xotcl(a)alice.wu-wien.ac.at > Message-ID: <49D6558E.200(a)activestate.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 03/04/2009 11:24 AM, Victor Mayevski wrote: >> I really like that XOTcl is being included with ActiveState >> distribution, and even updates via teacup are working. But there is >> one issue - why is it that the rest of XOTcl packages (comm, >> serializer etc) are not being included? > > The teapot is designed for individual packages (though they can have > dependencies). In building, it goes through the usual configure / make > / install steps. XOTcl only packages up the core library when it does > that. The other packages would be best handled separately somehow. Couldn't teacup provide the "--with-all=yes" configure flag so that the accompanying infrastructure is included? //stefan

2 1

Re: [Xotcl] Xotcl Digest, Vol 48, Issue 1
by Stefan Sobernig 04 Apr '09

04 Apr '09

Jeff, > Message: 2 > Date: Fri, 03 Apr 2009 11:29:34 -0700 > From: Jeff Hobbs <jeffh(a)activestate.com> > Subject: Re: [Xotcl] XOTcl packages > To: Victor Mayevski <vitick(a)gmail.com> > Cc: xotcl(a)alice.wu-wien.ac.at > Message-ID: <49D6558E.200(a)activestate.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 03/04/2009 11:24 AM, Victor Mayevski wrote: >> I really like that XOTcl is being included with ActiveState >> distribution, and even updates via teacup are working. But there is >> one issue - why is it that the rest of XOTcl packages (comm, >> serializer etc) are not being included? > > The teapot is designed for individual packages (though they can have > dependencies). In building, it goes through the usual configure / make > / install steps. XOTcl only packages up the core library when it does > that. The other packages would be best handled separately somehow. Couldn't teacup provide the "--with-all=yes" configure flag so that the accompanying infrastructure is included? //stefan

1 0

Re: [Xotcl] problem with new
by Stefan Sobernig 04 Apr '09

04 Apr '09

Victor, > Date: Tue, 24 Mar 2009 19:40:43 -0700 > From: Victor Mayevski <vitick(a)gmail.com> > Subject: [Xotcl] problem with new > To: Xotcl(a)alice.wu-wien.ac.at > Message-ID: > <eef838c10903241940v7870fd4djfa8b56bd4f6ba8d0(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > In my code, when trying to create a new autonamed instance of one of > my classes, I get the following error: > > [ MyClass new ] > invalid command name "::xotcl" > > I don't even know where to start looking for the cause of this error > since "new" is a built-in method of XOTcl. This error only happens > with this particular code, other code works fine. Any > tips/suggestions? I never encountered this issue (or sth. apparently similar) in an isolated piece of XOTcl code. And it is hard to tell from the two liner as this is most certainly rooted in your application-leve code (e.g. your MyClass declaration). Can you provide access to your application's code or compile a minimal, yet complete test script which reproduces the issue? //stefan

1 0

XOTcl packages
by Victor Mayevski 03 Apr '09

03 Apr '09

I really like that XOTcl is being included with ActiveState distribution, and even updates via teacup are working. But there is one issue - why is it that the rest of XOTcl packages (comm, serializer etc) are not being included? Thanks a lot

2 1

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 April 2009