itcl | An object-oriented extension to Tcl | Script Programming library
kandi X-RAY | itcl Summary
kandi X-RAY | itcl Summary
This is the 4.2.1 source distribution of Itcl, an object oriented extension for Tcl. Itcl releases are available from Sourceforge at:. This directory contains the source code, documentation, and test scripts for the itcl extension. This version is the next major release to follow Itcl 3.4. This version claims to be script level compatible with Itcl 3.4. Itcl is a freely-available open source package as in the past. You can do virtually anything you like with it, such as modifying it, redistributing it, and selling it either in whole or in part. See the file "license.terms" for complete information.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of itcl
itcl Key Features
itcl Examples and Code Snippets
Community Discussions
Trending Discussions on itcl
QUESTION
package require Itcl 3.2
...ANSWER
Answered 2021-Sep-06 at 15:48According to this guide, you do:
QUESTION
I am recently attempting to upgrade to TCL 8.6 (Yeah, several years late) from 8.5. I am running into an issue auto loading our itcl classes. In a number of our classes, we store the class methods in different files from the file with the class definition. Auto load was happy to handle this. In TCL 8.6, itcl is running into an issue auto loading the class methods. The class definition is autoloaded correctly, though. Is it still possible to have itcl autoload the class methods outside of the class definition file? If I call auto_load directly, the method will be loaded.
Note that for the example below, I did hand create the tclIndex file and it is not stored in auto_path.
testClass Definition File testClass.tcl
...ANSWER
Answered 2021-Aug-10 at 08:11The core of the issue is that methods in itcl 3 were basically commands, whereas methods in itcl 4 are categorically not (at the C level, they have a different signature; methods now have an extra argument that describes the invocation context, which describes the object in a way that respects dynamic behaviour). That cleans up a lot of the innards, but does mean that command-based mechanisms (such as autoloading) will not work.
I think the simplest fix is to just source
those auxiliary definition files explicitly at the end of your main class file (it really won't take that long under any sane scenario). To read in files relative to the current file, do:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install itcl
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page