Xotcl

xotcl@alice.wu.ac.at

2 participants
653 discussions

xodoc
by Jeff Levesque 19 Aug '09

19 Aug '09

Hi All, I hope this is still the right place for this, but I was wondering if anyone has any interest in some changes I've made to xodoc. I've really only added a couple things but they were big requirements for our documentation and I figured it might be this way for others as well. Here's the feature list and what I've completed so far: - Cleanup the output appearance/Make it look more like javadoc (In progress) - List inherited procedures for each class (Mostly finished) - Fix package (@ package provide ...) documentation (Mostly finished) - Create a side navigation bar of classes/procedures (similar to javadoc) (Not started) - Add HTML functionality to xodoc as needed (In progress) I've attached a sample of the files generated from my version of xodoc. If other people are interested I would go through and clean up the code before I made it available. - Jeff

2 2

Re: [Xotcl] xotcl crash
by Stefan Sobernig 25 Jul '09

25 Jul '09

> Message: 1 > Date: Fri, 24 Jul 2009 10:21:04 +0200 > From: Gustaf Neumann <neumann(a)wu.ac.at> > Subject: Re: [Xotcl] xotcl crash > To: Tibichte <zak(a)isa-software.com> > Cc: xotcl(a)alice.wu-wien.ac.at > Message-ID: <4A696EF0.7010906(a)wu.ac.at> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > 2- This forwarding method causes xotcl to crash: > > > > obj forward f2 list {%@end 13} %self %1 > > > > ? { obj f2 1 2 3 } > > There is a bug in the current xotcl versions when both > %@end and %1 is used, which will be fixed in the next release. > The %1 means that the first argument from the provided > argument list (here "1") will be placed at the given > position. The argument is consumed and the remaining > arguments (here "2" and "3") are appended to the arguments > from the forward definition. S The fact that %1 consumes = mutates the caller arg list and the %@POS substitution operates on the mutated state of the resulting (=final) list (kind of) made me think. And ... I guess I found the culprit of this crashy interaction (see the patch attached): once %1 consumes the first element of the caller arg list, the currently arg handling mechanism for forwards counts %1 as an extra arg in the overall arg list erroneously. however, it is rather a placeholder for an already counted arg (=the first in the caller arg list). This +1 overestimation in the internal assembly of the final arg list led to a memory access violation for the %@POS substitution under end offsets (end, end-1, end-2; in the Tcl sense of the word) because end offsets require a correct total args count internally (which used to report +1). as for the patch: it is a minor and fairly non-invasive change. all regression tests pass, i added some extra cases to test for the %1 + %@POS-under-end-offsets interaction. the patch can be applied to the a xotcl-1.6.3 source snapshot. cheers //stefan

1 0

xotcl crash
by Tibichte 24 Jul '09

24 Jul '09

Hello, I am experimenting with the xotcl method forwarding. 1- if I create a method forwarding f1: obj forward f1 list {%@end 13} %self ? { obj f1 1 2 3 } [list ::obj 1 2 3 13] Question: Why ::obj was inserted at the beginning but not at the end? 2- This forwarding method causes xotcl to crash: obj forward f2 list {%@end 13} %self %1 ? { obj f2 1 2 3 } Regards, Abderrazak Tibichte

2 1

Re: [Xotcl] two procs (-proc) for Attribute
by Mykhaylo Sorochan 20 Jul '09

20 Jul '09

Stefan, I was interested in case a). I was a little wrong with the syntax and was not able to build the statement right. Thanks. > # ad a) > # > Class create C -slots { > Attribute create a1 -proc assign args { > puts "[self]->[self proc] called" > next > } -proc get args { > puts "[self]->[self proc] called" > next > } > } > > C create c > c a1 1 > c a1 >

1 0

Re: [Xotcl] two procs (-proc) for Attribute
by Stefan Sobernig 20 Jul '09

20 Jul '09

Mykhaylo, > How to define several procs for one Attribute in class definition? > Particularly, I want to define both assign and get procs at once. i am not entirely confident that i grasbed the meanings of "serveral procs for one Attribute" and "at once". Do you mean: a) define 2 or more (per-object methods, i.e., procs) per slot object "at once"? b) define 2 (per-instance methods, i.e., instprocs) per family of slot objects "at once"? anyways, maybe some of the following is helpful to you: # # ad a) # Class create C -slots { Attribute create a1 -proc assign args { puts "[self]->[self proc] called" next } -proc get args { puts "[self]->[self proc] called" next } } C create c c a1 1 c a1 # # ad b) # Class MyAttribute -superclass Attribute \ -instproc assign args { puts "[self]->[self proc] called" next } -instproc get args { puts "[self]->[self proc] called" next } Class create D -slots { MyAttribute create a1 Attribute create a2 } D create d d a1 1 d a1

1 0

two procs (-proc) for Attribute
by Mykhaylo Sorochan 19 Jul '09

19 Jul '09

Hello, How to define several procs for one Attribute in class definition? Particularly, I want to define both assign and get procs at once. -- Regards, Mykhaylo Sorochan

1 0

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

Eclipse DLTK XoTcl Plugin.
by Patrick Finnegan 11 May '09

11 May '09

Is anyone in this group working on the Eclipse DLTK XoTcl Plugin?

1 0

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

← Newer
1
...
15
16
17
18
19
20
21
...
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