I have a script that I have been using for years. As far as I know I(file "/home/cecil/bin/teaTk.tcl" line 1)
did not change it. In the part that creates the Tk stuff I do have:
namespace import :::bindMultiple
This gives:
import pattern ":::bindMultiple" tries to import from namespace "" into itself while executing "namespace import :::bindMultiple"
invoked from within "source ${scriptDir}/teaTk.tcl"
(file "/home/cecil/bin/chooseTea.tcl" line 72)
Has there changed something in tclsh?
If the namespace import is wrong: what should it be?
Cecil Westerhof <[email protected]> wrote:(file "/home/cecil/bin/teaTk.tcl" line 1)
I have a script that I have been using for years. As far as I know I
did not change it. In the part that creates the Tk stuff I do have:
namespace import :::bindMultiple
This gives:
import pattern ":::bindMultiple" tries to import from namespace "" into itself while executing "namespace import :::bindMultiple"
invoked from within "source ${scriptDir}/teaTk.tcl"
(file "/home/cecil/bin/chooseTea.tcl" line 72)
Has there changed something in tclsh?
If the namespace import is wrong: what should it be?
::: is not a valid root namespace specifier (count the number of
colons).
Rich <[email protected]d> writes:(file "/home/cecil/bin/teaTk.tcl" line 1)
Cecil Westerhof <[email protected]> wrote:
I have a script that I have been using for years. As far as I know I
did not change it. In the part that creates the Tk stuff I do have:
namespace import :::bindMultiple
This gives:
import pattern ":::bindMultiple" tries to import from namespace "" into itself while executing "namespace import :::bindMultiple"
invoked from within "source ${scriptDir}/teaTk.tcl"
(file "/home/cecil/bin/chooseTea.tcl" line 72)
Has there changed something in tclsh?
If the namespace import is wrong: what should it be?
::: is not a valid root namespace specifier (count the number of
colons).
That was what I also thought. But changing it to two did not help.
As far as I know the code has not been changed.
It seems that it should be something like:
namespace import PACKAGE::bindMultiple
But until now I did not manage to find the correct package.
(I must confess that I am not the most proficient searcher.)
Does anyone know which package I should use?
Cecil Westerhof <[email protected]> wrote:(file "/home/cecil/bin/teaTk.tcl" line 1)
Rich <[email protected]d> writes:
Cecil Westerhof <[email protected]> wrote:
I have a script that I have been using for years. As far as I know I
did not change it. In the part that creates the Tk stuff I do have:
namespace import :::bindMultiple
This gives:
import pattern ":::bindMultiple" tries to import from namespace "" into itself while executing "namespace import :::bindMultiple"
invoked from within "source ${scriptDir}/teaTk.tcl"
(file "/home/cecil/bin/chooseTea.tcl" line 72)
Has there changed something in tclsh?
If the namespace import is wrong: what should it be?
::: is not a valid root namespace specifier (count the number of
colons).
That was what I also thought. But changing it to two did not help.
As far as I know the code has not been changed.
It seems that it should be something like:
namespace import PACKAGE::bindMultiple
But until now I did not manage to find the correct package.
(I must confess that I am not the most proficient searcher.)
Does anyone know which package I should use?
A google search for "tcl bindMultiple" (and forcing google to not
change it to "bind multiple" returned zero hits.
Is this possibly your own custom namespace from some other bit of code
you wrote?
But why ::dcblUtilities::bindMultiple was changed into :::bindMultiple
Cecil Westerhof <[email protected]> wrote:
But why ::dcblUtilities::bindMultiple was changed into :::bindMultiple
That looks like a search/replace gone wrong.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 15:21:07 |
| Calls: | 12,102 |
| Calls today: | 2 |
| Files: | 15,004 |
| Messages: | 6,518,048 |