Xotcl July 2006

xotcl@alice.wu.ac.at

9 participants
8 discussions

"Safe" deserialization
by Scott Gargash 26 Jul '06

26 Jul '06

There's been a lot of back-and-forth on the comp.lang.tcl and the Tcl'ers wiki lately about handling user input safely. Currently I'm using serialized XOTcl objects as user session data. The data gets saved to a file, and "source" is used to restore it. It all works well. But since the data is on the filesystem, it's possible for a user to edit the data or to load an arbitrary file ("Try this session..."). It seems like the standard Tcl answer is to source the session file in a safe interpreter, but (I think) that means I would need to alias all my XOTcl object constructors into the safe interpreter. Is this correct? Is there an easy way to do this? How do others deal with this sort of issue? Scott Notice The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying or distribution of the message, or any action taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please delete it and contact the sender immediately. Thank you.

1 0

XOTclLib
by Ben Thomasson 21 Jul '06

21 Jul '06

Hello all, Please that a look at http://xotcllib.sourceforge.net and reply with comments or critiques. XOTclLib is a library of debugging, logging, profiling, documentation, tracing, serialization, and unit-testing utilities. The documentation for the project is still in progress and will improve over time. Thanks, Ben Thomasson ben.thomasson(a)gmail.com

3 7

[volatile] documented in wrong section?
by Kristoffer Lawson 20 Jul '06

20 Jul '06

In the online reference manual, the volatile method is documented under Class, meaning it would be a class procedure. However the way it is demonstrated is: Object new -volatile Which would mean the object's [volatile] method is called. If [volatile] was actually a class procedure, then the object instance would not see it. In fact, it makes little sense that it would be a class procedure instead of one that can be applied to any object. Or have I missed something here? In a similar vein, can [volatile] be called at any point, not just during object instantiation? I might be getting an object returned from somewhere else and, in that proc, I may want to make it volatile so as to not have to worry about the point of destruction. / http://www.fishpool.com/~setok/

2 1

Re: [Xotcl] compilation problem
by Gustaf Neumann 20 Jul '06

20 Jul '06

Michael Schlenker schrieb: > Probably not if you add a Tcl_IncrRefCount Tcl_DecrRefCount for the > option Object. > > Michael > sure, i was just commenting the patch as it was posted in order to reduce potential suprises... -gustaf

1 0

compilation problem
by Bernd Eidenschink 20 Jul '06

20 Jul '06

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.

3 5

How do I get a parameters default-value?
by Murr, Florian 18 Jul '06

18 Jul '06

package require XOTcl namespace import xotcl::* # Let's say, I got: Class X -parameter { {p1 val1A} } X create x1 -p1 x1val1 # ... # Now I change the default-values X parameter { {p1 val1B} } X create x2 -p1 x2val1 # How do I get the current default-value 'val1B' for p1? # Note 'X info parameter' is no option, since after: X parameter {} puts "X parameter = [X info parameter]" X create x3 puts "x3 p1 --> [::x3 p1]" ;# still works. # So the default-values are remembered somewhere! # My guess was somewhere around '::xotcl::Class::Parameter', but I just # could not find, where? - and how to access them? # # Somehow there must be a better way to access the current default-values # then via some newly created dummy object?! # (May be even the "old" default-values 'val1A, val2A' (for ::x1) are still remembered somewhere?) # # regards, # - Florian

2 1

Asserts off/on
by Kristoffer Lawson 16 Jul '06

16 Jul '06

Responded to Uwe instead of the list. Here: Begin forwarded message: > From: Kristoffer Lawson <setok(a)fishpool.com> > Date: 11 July 2006 19:30:51 GMT+03:00 > To: Uwe Zdun <zdun(a)infosys.tuwien.ac.at> > Subject: Re: [Xotcl] Asserts off/on > > > On 11 Jul 2006, at 19:24, Uwe Zdun wrote: > >> The method "check" can be used to turn off assertions. The example >> from the tutorial: > > That is per-object. I am wondering if there is anything that would > be for everything. > > / http://www.fishpool.com/~setok/ > / http://www.fishpool.com/~setok/

2 8

Asserts off/on
by Kristoffer Lawson 11 Jul '06

11 Jul '06

Have I missed something, or is there no easy way of turning asserts off or on for all objects? It's common that during the development phase you want all the asserts turned on and, perhaps for performance reasons, turn them off when finished. I know it could be possible by overwriting the create method, or whatever, but I was looking for something... well ... less hacky. / http://www.fishpool.com/~setok/

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 July 2006