Xotcl July 2004

xotcl@alice.wu.ac.at

4 participants
4 discussions

RE: Private methods (was [Xotcl] build problem on solaris)
by Schofield, Bryan (GE Transportation) 28 Jul '04

28 Jul '04

> -----Original Message----- > From: Aamer Akhter [mailto:aakhter@gmail.com] > Sent: Tuesday, July 27, 2004 1:44 PM > To: Schofield, Bryan (GE Transportation) > Cc: xotcl(a)alice.wu-wien.ac.at > Subject: Re: [Xotcl] build problem on solaris [snip snip snip] > > One thing that popped into my mind was > how to do private variables and methods (i think this can be done via > the filters, but i haven't exactly figured them out yet) > > Thank-you to the developers for maintianing xotcl. Here is a quick hack example showing how to privatize a method. The instproc "priv" simply registers a method name to be considered private. Then a filter checks to see if the a method being called from somewhere outside of the object has been registered; If so, it throws. There is a lot of refinement that could be done, but at least this shows how a filter could be used to provide levels of protection. Making variables private is a little trickier. That might require the overloading variable mutators like "set", "lappend", "append" & so on. But one could make all thoses method private and then you've essentially made all variable private. Then use "parameters" for publicly accessible data, which is probably better any way since you are not allowing outsiders to directly change a variable, but rather providing them an interface to get & set the value of some piece of data. -- bryan --- package require XOTcl namespace import ::xotcl::* Class Foo Foo instproc init {args} { my array set priv {} my priv bar } Foo instproc bar {} { puts "[self] BAR!" } Foo instproc ack {} { my bar puts "[self] ACK!" } Foo instproc priv {method} { my set priv($method) 1 } Foo instproc checkAccess {args} { puts "check access [self] [self calledproc] called from [self callingproc]" if {[my exists priv([self calledproc])] && ([self callingproc] eq "")} { return -code error "[self calledproc] is private" } next } Foo instfilter checkAccess Foo f f ack # This next line will generate an error. f bar

2 1

RE: [Xotcl] build problem on solaris
by Schofield, Bryan (GE Transportation) 27 Jul '04

27 Jul '04

I had that problem at as well. I didn't care to make xowish or xotclsh, I ended up commenting portions of the make file out to get it to work. Specifically, I commented out "binaries", "install", and part of "libraries" target. I don't mean to speak for Gustaf, but maybe give this version a try: http://media.wu-wien.ac.at/download/xotcl-1.2.1.tar.gz I don't think it's quite ready for primetime, since Gustaf & Co. are adding a few enhancements. But I think all that remains is documentation. I've been using it & testing out the new features for a about 2 months and consider it stable. That version also has a better build & configuration system and compiles with out complaint fine for me (which is the only reason I'm mentioning it, it was a painful to get the last publicly released version to compile on Solaris). I'm sure the XOTcl guys will correct me if I'm wrong. I noticed you posted a question on the IncrTcl mailing list earlier today about "unknown" handlers. I think you'll find that XOTcl's unknown handler is fantastic. I've used IncrTcl extensively, but over the last 6 months or so I've began using XOTcl instead. I now prefer XOTcl greatly to IncrTcl. After using it, I feel so constrained with IncrTcl by having to fully define my classes, and thus my object behavior, a head of time. The flexibility of XOTcl is phenomenal. -- bryan > -----Original Message----- > From: xotcl-admin(a)alice.wu-wien.ac.at > [mailto:xotcl-admin@alice.wu-wien.ac.at]On Behalf Of Aamer Akhter > Sent: Tuesday, July 27, 2004 12:42 PM > To: xotcl(a)alice.wu-wien.ac.at > Subject: [Xotcl] build problem on solaris > > > Folks, > > I'm having a a makefile problem on solaris (the linux build went fine) > > gcc -pipe -shared -o libxotcl1.2.so so/xotcl.o so/xotclError.o > so/xotclMetaData.o so/xotclObjectData.o so/xotclProfile.o > so/xotclTrace.o so/xotclUtil.o so/xotclShadow.o so/xotclCompile.o > so/aolstub.o so/xotclStubInit.o > -L/auto/nsite-mmpls/users/aakhter/ats4.0/lib -ltclstub8.4 > : libxotcl1.2.so > /bin/bash: -c: line 1: syntax error near unexpected token `;' > /bin/bash: -c: line 1: `if test ! "x" = "x" ; then for dir in ; do > if (cd $dir; make binaries) ; then true ; else exit 1 ; fi ; done; > fi;' > > which is (with make -d): > > Finished prerequisites of target file `binaries'. > Must remake target `binaries'. > Putting child 0x00068080 (binaries) PID 17840 on the chain. > Live child 0x00068080 (binaries) PID 17840 > /bin/bash: -c: line 1: syntax error near unexpected token `;' > /bin/bash: -c: line 1: `if test ! "x" = "x" ; then for dir in ; do > if (cd $dir; make binaries) ; then true ; else exit 1 ; fi ; done; > fi;' > > makefile: > > binaries: $(BINARIES) $(XOTCLSH) $(XOWISH) pkgIndex.tcl > @if test ! "x$(subdirs)" = "x" ; then \ > for dir in $(subdirs) ; do \ > if (cd $$dir; $(MAKE) $@) ; then true ; else exit 1 ; fi ; \ > done; fi; > > > has anybody run into this problem already? > > -- > Aamer Akhter / aakhter(a)gmail.com > _______________________________________________ > Xotcl mailing list - Xotcl(a)alice.wu-wien.ac.at > http://alice.wu-wien.ac.at/mailman/listinfo/xotcl >

2 1

build problem on solaris
by Aamer Akhter 27 Jul '04

27 Jul '04

Folks, I'm having a a makefile problem on solaris (the linux build went fine) gcc -pipe -shared -o libxotcl1.2.so so/xotcl.o so/xotclError.o so/xotclMetaData.o so/xotclObjectData.o so/xotclProfile.o so/xotclTrace.o so/xotclUtil.o so/xotclShadow.o so/xotclCompile.o so/aolstub.o so/xotclStubInit.o -L/auto/nsite-mmpls/users/aakhter/ats4.0/lib -ltclstub8.4 : libxotcl1.2.so /bin/bash: -c: line 1: syntax error near unexpected token `;' /bin/bash: -c: line 1: `if test ! "x" = "x" ; then for dir in ; do if (cd $dir; make binaries) ; then true ; else exit 1 ; fi ; done; fi;' which is (with make -d): Finished prerequisites of target file `binaries'. Must remake target `binaries'. Putting child 0x00068080 (binaries) PID 17840 on the chain. Live child 0x00068080 (binaries) PID 17840 /bin/bash: -c: line 1: syntax error near unexpected token `;' /bin/bash: -c: line 1: `if test ! "x" = "x" ; then for dir in ; do if (cd $dir; make binaries) ; then true ; else exit 1 ; fi ; done; fi;' makefile: binaries: $(BINARIES) $(XOTCLSH) $(XOWISH) pkgIndex.tcl @if test ! "x$(subdirs)" = "x" ; then \ for dir in $(subdirs) ; do \ if (cd $$dir; $(MAKE) $@) ; then true ; else exit 1 ; fi ; \ done; fi; has anybody run into this problem already? -- Aamer Akhter / aakhter(a)gmail.com

1 0

Updates for XOTclIDE and Xdobry
by Artur Trzewik 13 Jul '04

13 Jul '04

Hi There is new version 0.61 of XOTclIDE ready on: http://www.xdobry.de/xotclIDE Changes: - new plug-in. I18N (Internationalization) Helper that can scan sources after msgcat-library expresions, helps by translation and produce msg-catalogs. - support of Oracle and MS Sql Server as version control database - small bug-fixes - requires Tcl8.4 Xdobry (database tool) in version 0.40 contains new features: - can be used as database schema creation and manipulation tool - can migrate data between all supported databases - can dump databases to xml-dump and import it to every supported database. - many bug fixes and refactoring - supports: MS Access, Oracle, MS SQL Server - updated documentation - requires Tcl8.4 - deployed also as starkits for windows and linux. Artur Trzewik

1 0

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 2004