Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Helmut Giese <hgiese@ratiosoft.com>
Newsgroups: comp.lang.tcl
Subject: A TclOO question
Date: Tue, 16 Jul 2024 15:26:20 +0200
Organization: ratiosoft
Lines: 23
Message-ID: <47rc9jdmepbpbfa7l64872m7nujuvs2g4h@4ax.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 16 Jul 2024 15:26:19 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="099f063b840f20be6e947043757b4a99";
	logging-data="1361622"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/BkeMBrmlI40VlPUKsH0Rm"
Cancel-Lock: sha1:Z8Sod20wnfpKgJ06YE7lQoQ+7hE=
X-Newsreader: Forte Free Agent 1.93/32.576 English (American)
Bytes: 1859

Hello out there ,
I found XOTclLight (https://github.com/xdobry/xotcl-light ) which is
an XOTcl compatible implementation via TclOO. My hope was that with it
XOTcl's mysterious error messages would be traceable since the calls
wouldn't be buried in XOTcl's binary.
Alas, it errored out with
	may not change classes into an instance of themselves
on the line
	oo::objdefine Class class Class

While this intuitively makes sense I wonder:
1) Maybe TclOO's syntax has changed since then (2015)? After all, a
man who knows enough about OO systems to implement one in terms of the
other isn't likely to release a package which is evidently unusable.
2) What does the statement cited above try to achieve? And, most
important, what magic can achieve it?

I figured that it attempted to replace the XOTcl command 'Class' with
its own definition so I changed in the script and the call above
'Class'  to 'NewClass' - but to no avail.

Any idea or help will be greatly appreciated
Helmut