Weblog Page

From: Catherine Letondal <letondal_at_pasteur.fr>
Date: Sat, 14 Jul 2001 08:10:58 +0200

Hi,

Alexis Gambis, a student having spent his Internship with us at Pasteur,
has just finished his project :
Interaction between the User and Heijne's membrane topology prediction
algorithm Toppred

We thought that the mixin technique could be useful to enhance the
interaction between user and algorithm by the mean of supplemental
user input taken into account without modifying the algorithm.

His results are summarized here:
http://www-alt.pasteur.fr/~letondal/biok/usermixin.html

-- 
Catherine Letondal -- Pasteur Institute Computing Center

From: Gustaf Neumann <Gustaf.Neumann_at_wu-wien.ac.at>
Date: Tue, 6 Feb 2001 00:05:10 +0100 (CET)

KL> Btw. any ideas when 8.4 will be out? The bug with the destruction of
KL> objects and error handling is causing some small headaches in the
KL> debugging phase of code here. I really hate to pressure you like this, but
KL> I need to be able to look forward to a bright future when I get into that
KL> situation, so I can say "Oh, it'll be alright soon" when I stumble across
KL> that situation. No panics though.

 we have done a substantial redesign of object and class
 creation/recreation/deletion. Many things that were hard-wired before
 are now modifiable from within XOTcl. We have now a solution that
 looks promising to both, the "[self] destroy" problems and the issue
 of recreating classes and objects. We have still the hope to get the
 next release this week done. i can't name dates for now, but 0.84
 will be out soon.

 -gustaf

From: Laurent Duperval <laurent.duperval_at_netergynet.com>
Date: Wed, 13 Dec 2000 09:33:14 -0500 (EST)

On 13 Dec, Kristoffer Lawson wrote:
> Well proc is something you use if you want a procedure that exists
> only in that instance of an object. So if you want a procedure for
> class Foo which doesn't appear in instances of Foo then you use "proc".
> The same applies if you want to add a procedure to a single object.
> I must admit I don't really use it much myself but it's good to have it
> when you do need it, and really works with the dynamic nature of the
> language.
>

Ah! So it's somewhat analogous to static methods in Java. Except that is't
dynamic. :-)

L

-- 
MY EMAIL ADDRESS HAS CHANGED --> UPDATE YOUR ADDRESSBOOK
Laurent Duperval                   "Montreal winters are an intelligence test,
Netergy Networks - Java Center            and we who are here have failed it."
Phone: (514) 282-8484 ext. 228                                   -Doug Camilli
mailto:laurent.duperval_at_netergynet.com           Penguin Power!

From: Uwe Zdun <uwe.zdun_at_wu-wien.ac.at>
Date: Fri, 16 Apr 2004 17:44:59 +0200

Hi Attilio!

Attilio Dona` wrote:

>
> Hy,
>
> Thanks to XOTcl I'm rethinking the OO paradigm and doing metaprogramming
> easier.
>

thanks!!

> 1. Parameter introspection
>
> I use the Metaclass concept to model metainfos and use the parameter
> command to add meta-attributes runtime.
> As already You pointed out the parameter introspection (className info
> parameter) mechanism is not correct, so it is needed some parsing, with
> euristic regexp, to extract the parameters info.
>
> Also the command:
>
> className info parameter parameterName
>
> doesn't work as expected, because it ignores parameterName
>
> Have you planned to release in the near future the fix to this problem?
>
I agree, we should fix this for the next release ...

>
> 2 Parameter strange behavoir
>
> When using Parameter command I have noticed same strange behavoirs, for
> examples:
>
> case 1:
> Class X -parameter {{-x 100}}
> ::X
>
> case 2:
> Class X -parameter [list {-x 100}]
> wrong # args: ....
>
> case 1 and 2 are perfectly equivalent, so I think there is same strange
> parsing inside a C function. Also note that this is true only for
> "negative"
> attribute, ie: Class X -parameter [list {x 100}] work as expected.
>
this is because -... has a meaning for the paramters, like widget
options,
and is substituted, if you don't put two brackets around it {{..}} ...
see language
reference for more explanation.

As this is a normal substitution in Tcl, you can get around this problem
by backslashing
the "-":

Class X -parameter [list {\-x 100}]

this works.

Uwe

> Attilio
>
>
>
>
> --------------------------------------------------------------------
> 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_at_telecomitalia.it
> <mailto:webmaster_at_telecomitalia.it>.
> Thank you
> www.telecomitalia.it
> <http://www.telecomitalia.it>
> --------------------------------------------------------------------

From: Laurent Duperval <lduperval_at_videotron.ca>
Date: Tue, 04 Mar 2003 23:18:26 -0500 (EST)

On 3 Mar, Kristoffer Lawson wrote:
> On Mon, 3 Mar 2003, Artur Trzewik wrote:
>
>> all people that use atkdebugger should rebuild tcl with new
>> tcl8.4.1-atkdebugger.patch
>
> Just a silly sidenote, but I always find the name "atkdebugger" so funny.
> You see ATK in Finnish is a very frequently used term for computing,
> literally "Automatic Information Management". So I was really surprised
> to see it used in foreign software, until I realised it was probably
> from your name. Still, it fits quite nicely! :-)
>

Oh! I thought it was "A Tk Debugger".

L

-- 
Laurent Duperval <mailto:lduperval_at_videotron.ca>
If you're in a vehicle going the speed of light, what happens when you
turn on the headlights?
                                                          -
Tap Into Your Full Potential/Puisez Dans Votre Plein Potentiel
My/Mon Club:          http://www.geocities.com/tmsuroit
My/Mon District:      http://www.toastmastersdistrict61.org
My/Mon Organisation:  http://www.toastmasters.org

From: <mail_at_xdobry.de>
Date: Fri, 11 Feb 2011 08:37:42 +0100 (CET)

Hi Krzysztof!


I have run also into this problem (trap).
Threads in Tcl are different than in Java or C#.
The tcl threads are more like new independent processes (at Tcl level).

New Thread in Tcl is just new Interpreter. Interpreter is environment to run Tcl
code. (see command interp)

Every interpreter/thread has all internal structures (Tcl methods and verialbes)
independent to another interpreter.

You can not share XOTcl Objects between interpreters because object name is just
string reference to internal structure of object.
Serializing object is probably not the solution for this what you need.
You can share only values but not references.

The solution would be create in each thread separate bundle of XOTcl objects
that can communicate with each other by sharing values (just strings)

My personal experience is not to use threads at all.
You can use internal event handler of Tcl to simulate parallel processing.
For example for GUI to program not freezing GUI or aborts buttons.

Use commands:
after
update
vwait (Works also with XOTcl variables)

I have programmed spell checker for editor which runs in "update" loop and for
user it seems to be completely parallel. Using tcl threads for it will be
overkill.
Also programming IO operations (for example Tcl Server) with events is better
then using threads.
Tcl has good support for asynchronous IO operations.

Tcl has very good event handling loop that is nearly the same that old OS
uses (Windows 3.1) to simulate parallel processing.
See tcl wiki for some examples.

Artur









Krzysztof Frukacz <frukacz.krzysztof_at_gmail.com> hat am 10. Februar 2011 um 14:27
geschrieben:

> Hello again,
>
> I am trying to add multi-threaded support for my application. I now face
> a problem witch combining XOTCl and Thread. The problem is that
> ::thread::create creates a new instance of interpreter which has own
> variables. I can have variables shared between threads using ::tsv
> functions. So here is how it looks:
>
> 1. Thread #1 creates object myObject and stores in a shared variable:
> ::tsv::set array1 key1 [MyClass myObject]
>
> 2. Thread #2 gets the shared variable and tries to call a proc defined
> for MyClass:
> set localVar [::tsv::get array1 key1]
> $localVar doSomething
>
> At this point second thread will throw en exception saying:
> Unknown command 'myObject'
>
> What would be the proper way to "register" the object myObject (which
> already exists) in another thread?
>
> --
> Krzysztof
> _______________________________________________
> Xotcl mailing list
> Xotcl_at_alice.wu-wien.ac.at
> http://alice.wu-wien.ac.at/mailman/listinfo/xotcl

From: Arthur Fleischmann <arthur.fleischmann_at_chello.at>
Date: Tue, 5 Nov 2002 18:41:33 +0100

Hallo!

Da ich leider zuhause kein Linux installiert habe, wollte ich die Win-Version von XOTcl installieren...
Hat das irgendjemand geschafft? Bei mir haut's leider nicht ganz hin. Ich kann zwar mit Startmenü-Ausführen-xotclsh bzw. Startmenü-Ausführen-tclsh die jeweiligen Shells aufrufen, das gleiche funktioniert aber leider nicht aus dem DOS-Fenster (Eingabeaufforderung), obwohl die PATH-Variablen richtig gesetzt sind.Das wäre aber notwendig, um ein *.tcl Programm aus dem DOS-Fenster auszuführen.

Die eigentliche Installation hat gaube ich funktioniert, bin so vorgegangen, wie auf der Homepage beschrieben, zuerst Tcl (ActiveTcl 8.3.4.4) installiert, dann XOTcl runtergeladen + entpackt, dann InstallWin ausgeführt: es öffnet sich ein Fenster "InstallWin" ohne Inhalt (?) aber xotclsh.exe befindet sich danach im Verzeichnis C:\Programme\Tcl\bin - das sollte also passen.

Kann mir vielleicht irgendjemand weiterhelfen - vielleicht gar der geschätzte LV-Leiter? :)

Danke, mfG,

Arthur

PS: Windows Version ist Win2kPro

From: Kristoffer Lawson <setok_at_fishpool.com>
Date: Mon, 1 Aug 2005 22:16:18 +0300

On 1 Aug 2005, at 13:46, Gustaf Neumann wrote:

>
> The best fix is to remove twice the word "static" before
> XOTcl_ThreadExitProc.
> I've fixed this some time ago, when Tiger came out.. we should
> release most
> probably a maintenance release soon.
>

Hm, are nested functions a part of C99? If not, I would prefer to see
this moved to the top level. Strict ISO C adherence is something I
generally prefer.

            / http://www.fishpool.com/~setok/

From: Rick Hedin <rhedin_at_aquifer.geology.uiuc.edu>
Date: Thu, 16 May 2002 08:16:33 -0500

Hello. My friends are trying to convince me of the value of functional
programming. Writing safer and clearer programs sounds good, but I am not
inclined to learn Haskell.

Xotcl is a pretty flexible beast. Can I do functional programming in it?
It seems as though classes are a variety of object in Xotcl, so that will be
an advantage for passing classes around, but what else am I missing? I
suspect that Gustaf and Uwe thought about functional programming when they
designed their beast. Can I find out what their thoughts were?


        Regards,

        Rick

From: Uwe Zdun <uwe.zdun_at_wu-wien.ac.at>
Date: Tue, 13 May 2003 11:53:36 +0200

It does not solve the main problems solved by check_library_path:
to include the env(XOTcl) variable and use the local directory
when you are in it so that you don't necessarily have to install. The
rest of the code (in the second else part) is only used to set the
xotcl::lib variable correctly. Again: this variable is not really needed.
At the moment, it is only an information for the programmer.

we can think about getting rid of the variable, maybe.

--uwe



On Tuesday 13 May 2003 10:50, Gustaf Neumann wrote:
> On Monday 12 May 2003 23:27, MichaelL_at_frogware.com wrote:
> > I don't know if this helps, but my approach was to add the following in
> > xotcl-1.0.2/pkgIndex.tcl:
>
> Good idea!
>
> the following is more generic an should work (if it placed
> into the installed directory of the xotcl library) platform indepently.
>
> We should think a little about what to do to execute xotcl
> in the noninstalled case (e.g.
> - putting this into xotcl-$(VERSION)/library,
> - add a simple pkgIndex.tcl to xotcl-$(VERSION) to load the shared lib
> - add xotcl-$(VERSION) to auto_path
> ) and to produce the attached one on install....
> This is the way we should go.
>
> -gustaf
>
> ============================================================
> package ifneeded XOTcl 1.0 [list load \
> [file join $dir .. libxotcl1.0[info sharedlibextension]] XOTcl]
>
> set _dir_ $dir
> foreach index [glob -nocomplain [file join $dir * pkgIndex.tcl]] {
> set dir [file dirname $index]
> source $index
> }
> set dir $_dir_
> unset _dir_
> ============================================================

-- 
Uwe Zdun
Department of Information Systems, Vienna University of Economics
Phone: +43 1 313 36 4796, Fax: +43 1 313 36 746
zdun_at_{xotcl,computer,acm}.org, uwe.zdun_at_wu-wien.ac.at