Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

which tcllib version for tcl 8.0

15 views
Skip to first unread message

David Bariod

unread,
Dec 15, 2006, 7:09:44 AM12/15/06
to
Hi all tcler's,

I'm stuck with an embedded old tcl 8.0 in the vxWorks host tools
I really miss a lot of feature of the tcllib (especally the cmdline
one)
Does someone know which is the most up-to-date release of the tcllib
which is compatible with the 8.0 tcl version ?

David Bariod.

Larry W. Virden

unread,
Dec 15, 2006, 7:23:06 AM12/15/06
to

Well, I just looked through http://tcllib.sf.net/'s browse cvs option
and found that only version 1.1 of cmdline module worked with Tcl 8.0.
Everything else lists 8.2 as the oldest version. However, you could
always download the code, modify the satisfies, and try it out to see
what newer features it requires. It COULD be that it was only tested
with 8.2 and newer. Or perhaps you could implement some sort of
backwards compatibility module for making the required features
available. Or maybe you could investigate writing some sort of tcl 8.0
extension that loads a newer version tcl and communicates with it!

Cameron Laird

unread,
Dec 15, 2006, 10:22:52 AM12/15/06
to
In article <1166185386.4...@l12g2000cwl.googlegroups.com>,

Larry's right.

I'll add a little detail: several packages definitely only
work with 8.2 or later; there were pertinent bug fixes.

At the same time, for a situation like Mr. Bariod's, it's
important to realize how loosely coupled Tcllib is, AND how
easy it is to work with it as a pure-Tcl resource. Unless
your vxWorks application is very unusual, it doesn't need
all of Tcllib. Do what Larry counsels: install, and
investigate.

Larry W. Virden

unread,
Dec 15, 2006, 12:08:13 PM12/15/06
to

Larry W. Virden wrote:
> maybe you could investigate writing some sort of tcl 8.0
> extension that loads a newer version tcl and communicates with it!

I've been thinking about this one today.Each application has its own
requirements, but perhaps there is something here that you could do. It
would work something similar to Tk or the tcllib comm module, perhaps,
and procs in your tcl8.0 program would, internally, "call out" to the
tcl 8.5 process (with some sort of shared memory, perhaps, in common,
or some other shared communication channel).

David Bariod

unread,
Jan 5, 2007, 8:01:22 AM1/5/07
to
Larry W. Virden a écrit :

Thanks for your advice.
I think I will look at the old tcllib and check
if it is enough for my needs, as you correctly guess
I do not need the complete tcllib.

0 new messages