Weblog Page

From: Gustaf Neumann <neumann_at_wu-wien.ac.at>
Date: Thu, 20 Jul 2006 10:27:16 +0200

Bernd,

to be sure, i just built xotcl 1.4.0 against 8.4.13, and it worked
without a glitch.
Can it be that configure picks up a wrong version of tcl? The function
TclIncrVar2
has its prototype in tclIntDecls.h, which does not seem to be used in
your case
(... implicit declaration ...)

To be sure, use the switches like in:

    http://www.openacs.org/xowiki/pages/en/xotcl-core#install

if this does not help, what is your build environment (OS and cc)?

-gustaf

Bernd Eidenschink schrieb:
> Hi!
>
> I try to compile XOTcl 1.4.0 against Tcl 8.4.13 for using it with Naviserver
> (Head).
>
> I do the usual
> ./configure --enable-threads --prefix=/usr/local/ns
>
> and after that, make, that barks:
>
> [...]
> ./generic/xotcl.c: In function ‘AutonameIncr’:
> ./generic/xotcl.c:1718: warning: implicit declaration of
> function ‘TclIncrVar2’
> ./generic/xotcl.c:1718: warning: assignment makes pointer from integer without
> a cast
> ./generic/xotcl.c: In function ‘Xotcl_Init’:
> ./generic/xotcl.c:11310: warning: dereferencing type-punned pointer will break
> strict-aliasing rules
>
> [...]
> ./generic/xotclStubLib.c: In function ‘Xotcl_InitStubs’:
> ./generic/xotclStubLib.c:67: warning: dereferencing type-punned pointer will
> break strict-aliasing rules
> rm -f libxotclstub1.4.0.a
> ar cr libxotclstub1.4.0.a xotclStubLib.o
> ranlib libxotclstub1.4.0.a
> couldn't load file "././libxotcl1.4.0.so": ././libxotcl1.4.0.so: undefined
> symbol: TclIncrVar2
> while executing
> "load ././libxotcl1.4.0.so XOTcl"
> ("package ifneeded XOTcl 1.4.0" script)
> invoked from within
> "package require XOTcl"
> (file "./library/lib/makeDoc.xotcl" line 2)
> make: *** [doc/langRef-xotcl.html] Fehler 1
>
> I can't swear my build environment is sane as I did a lot of installs and
> tests these days, but I'll try everything you tell me...
>
> Thanks,
> Bernd.
>
> _______________________________________________
> Xotcl mailing list
> Xotcl_at_alice.wu-wien.ac.at
> http://alice.wu-wien.ac.at/mailman/listinfo/xotcl
>

From: Victor Mayevski <vitick_at_gmail.com>
Date: Sun, 19 Apr 2015 13:21:55 -0700

Recently I encountered a need for two methods in my code:

"info siblings"
"info root" -- similar to "info parent" but travels down the object tree
to find the first object or root (of a tree OR a branch).

I realize that it is very trivial to script them in myself but I am dealing
with thousands (if not millions in the future) of objects and would like to
squeeze as much performance from the code as possible. Hence, I propose to
add those methods in C code (to NSF), provided that coding them in C will
indeed speed things up. Also, having those methods seems to be natural,
just like having "info parent" or "info children".

Another proposal, (tongue-in-cheek, since it probably benefits only my
code), is to add a timestamp (microseconds) to every object upon creation.
I have a need to list the object (thousands, if not millions) in the order
of creation. Again, it is trivial to script it in, but performance is an
issue.


Thanks

From: Andreas Kupries <andreask_at_activestate.com>
Date: Tue, 06 Aug 2013 08:57:49 -0700

20'th Annual Tcl/Tk Conference (Tcl'2013)
http://www.tcl.tk/community/tcl2013/

September 23 - 27, 2013
Bourbon Orleans Hotel
New Orleans, Louisiana, USA
http://www.bourbonorleans.com/

I am pleased to announce that registration for the Conference is now
open at

        http://www.tcl.tk/community/tcl2013/reg.html

To book a room at the conference hotel at reduced rates please follow
the instructions on that page. Note that the offer of reduced rates
expires on August 19 (In 2 weeks). Book NOW.

Our schedule can be found at

        http://www.tcl.tk/community/tcl2013/schedule.html

Conference Committee

Clif Flynt Noumena Corp General Chair, Website Admin
Andreas Kupries ActiveState Software Inc. Program Chair
Cyndy Lilagan Nat. Museum of Health & Medicine, Chicago Site/Facilities Chair
Arjen Markus Deltares
Brian Griffin Mentor Graphics
Donal Fellows University of Manchester
Gerald Lester KnG Consulting, LLC
Jeffrey Hobbs ActiveState Software Inc.
Kevin Kenny GE Global Research Center
Larry Virden
Mike Doyle National Museum of Health & Medicine, Chicago
Ron Fox NSCL/FRIB Michigan State University
Steve Landers Digital Smarties

Contact Information tclconference_at_googlegroups.com


Tcl'2012 would like to thank those who are sponsoring the conference:

ActiveState Software Inc.
Buonacorsi Foundation
Mentor Graphics
Noumena Corp.
SR Technology
Tcl Community Association

From: Gustaf Neumann <neumann_at_wu-wien.ac.at>
Date: Thu, 26 Aug 2004 22:02:33 +0200

Dear XOTcl Community,

This is a minor fix release relative to 1.3.0. This release fixes a few
problems introduced in 1.3.0 (invocation of checking procs in
nonpositional argument) and has a better build support for building
XOTcl outside of the source tree, the tar files are now dist-cleaned.
  
Best regards,
 
Gustaf Neumann
Uwe Zdun

-- 
Univ.Prof. Dr.Gustaf Neumann
Abteilung für Wirtschaftsinformatik und Neue Medien
Wirtschaftsuniversität Wien, Augasse 2-6, 1090 Wien

From: Kristoffer Lawson <setok_at_fishpool.com>
Date: Wed, 30 May 2001 17:55:29 +0300 (EEST)

On Wed, 30 May 2001, Uwe Zdun wrote:

>
> We would propose a new:
>
> Class instproc newChildOf {obj args} {
> ::set name [[self] autoname -instance [namespace tail [self]]]
> ::eval [self] create ${obj}::$name $args
> }
>
> which would be almost identical to newChild, but allows for specifying an
> object name...

Yes, that sounds good. If you think that will be the syntax for the next
XOTcl release then I'll change what I currently use to do the above.

         - ---------- = = ---------//--+
         | / Kristoffer Lawson | www.fishpool.fi|.com
         +-> | setok_at_fishpool.com | - - --+------
             |-- Fishpool Creations Ltd - / |
             +-------- = - - - = --------- /~setok/

From: Michael Schlenker <schlenk_at_uni-oldenburg.de>
Date: Wed, 07 May 2003 09:54:12 +0200

Hi,

i looked at the persistence example and saw that there is no Metakit
storage class yet. This would be a nice addidition especially if using
XOTcl with tclkit (that has metakit already embedded).

What has to be done to implement metakit storage? Just provide the few
abstract instprocs from /library/store/Storage.xotcl ?

Michael Schlenker

From: Jeff Hobbs <jeffh_at_ActiveState.com>
Date: Mon, 29 Nov 2004 19:28:07 -0800

Attached is a patch to xotcl to make it build better. The
changes are to correct the build and install both on unix
and Windows.

The fixes correct:

* installation when built outside source directory
* build and installation on Windows using TEA
* more clarity during install-libraries

The addition of VISUAL_CC to the defines on Windows
highlights a generally incorrect usage of Windows-checking
constructs. You can add things like

#ifdef _MSC_VER

in your C code, or better yet it should simply switch on:

#if defined(WIN32)

which tcl.h defines, and for the USE_MALLOC case, something
like this should suffice:

#if defined(WIN32) && !(defined(__GNUC__)

but the changes I made work, just in a less favorable way.

  Jeff Hobbs, The Tcl Guy
  http://www.ActiveState.com/, a division of Sophos

From: Gustaf Neumann <neumann_at_wu-wien.ac.at>
Date: Fri, 04 Jan 2008 13:19:43 +0100

Murr, Florian schrieb:
> Dear XOTcl-guys!
> The script below might illustrate another XOTcl bug.
>

Dear Florian,

That's not a bug. [info level 0] does not return the name of the method
in all situations, since "info level" is not xotcl-aware and is not touched
by the xotcl implementation. In situations, where - from the Tcl point
of view - the cmd "next" calls a method, "info level 0" returns "next".
There is nothing wrong about this.
> X instproc fun {w} { puts "[self] [info level 0]"; button $w.b;
> return $w.b }
>
In cases, where you want to output the name of the active method, use
XOTcl's callstack introspection with - in this case - "self proc". Change
your code as follows to obtain the method name in the outpt.

X instproc fun {w} {puts "[self] [self proc]"; button $w.b;
return $w.b }

best regards
-gustaf neumann

From: Gustaf Neumann <neumann_at_wu-wien.ac.at>
Date: Wed, 4 Jul 2001 14:46:10 +0200

 Dear List members,

 Last week, the hostname (actually the alias) of the machine
 running the XOTcl list has changed. please use for the main
 entry page of the xotcl list

   http://alice.wu-wien.ac.at/mailman/listinfo/xotcl

 and to access the archives, please use

   http://alice.wu-wien.ac.at/pipermail/xotcl/

 instead of the URLs with the hostname wi.wu-wien.ac.at

 Send submissions to
   xotcl_at_alice.wu-wien.ac.at

 best regards

-gustaf neumann

From: Kristoffer Lawson <setok_at_fishpool.com>
Date: Thu, 8 Sep 2005 13:33:56 +0300 (EEST)

On Thu, 8 Sep 2005, Gustaf Neumann wrote:

> i have started some work towards turning packages into objects, where a
> package
> is an instance of a class Package. This allows in general to

OK, this sounds interesting. I think the most important for something like
this is that it should be clearly stated why it is better than the normal
Tcl mechanism, seeing as it would kind of compete with it (and more
mechanisms isn't always best if one wants to keep the code clean).

>> The problem with this is that classes are not automatically searched for
>> in the same package. That is if Class A depends on Class B (A is B's
>> sub-class), B needs to be read in before A is read. In Java it is enough
>> that they are in the same package, they'll be found. With XOTcl you need
>> to build a kind of stub file that represents the package and which then
>> sources in all the other necessary files in the required order.
>
> a few remarks to this:
> - what's wrong with "package req package-providing-class-B" in the package
> containing class A?

That is two fine. I would prefer to have lots of related classes being
part of the same Tcl package. For that, I have to build a stub package
which then includes the rest in the appropriate order (or using some kind
of sub-packaging).

So it doesn't really reflect the Java model, which is fairly
straightforward.

And just for the record: I'm not a big Java advocate. In fact I think they
have made serious design mistakes in many areas. Even in packages they
forgot a very important part of the picture: version numbering.

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