Tablelist under 8.5
crv...@up-link.net
have a script that works under 8.4 but under 8.5 I get an error that
says Tablelist is not found though teapot says that it is installed.
What's the deal?
Csaba Nemethi
If your scripts contain "package require Tablelist", please change this
statement to become "package require tablelist". This is because for
some teapot-related technical reason the ActiveTcl distribution no
longer supports the package "Tablelist" (it only supports the
all-lowercase version "tablelist").
In the next Tablelist release I will change the demo scripts to use
"package require tablelist" instead of "package require Tablelist", and
I will also include a remark concerning this distribution-specific aspect.
--
Csaba Nemethi http://www.nemethi.de mailto:csaba....@t-online.de
Jeff Hobbs
For ActiveTcl and the core in general, we actually plan to introduce a
TIP that removes the case-sensitivity of package names. It is fairly
useless in practice, and has confused many users of various
extensions.
Jeff
Gerhard Reithofer
> On Nov 9, 8:55 am, Csaba Nemethi <csaba.neme...@t-online.de> wrote:
> > crv...@up-link.net schrieb:
> >
> > > I am trying to use tcl 8.5 after having used 8.4 for some time now. I
...
> > In the next Tablelist release I will change the demo scripts to use
> > "package require tablelist" instead of "package require Tablelist", and
> > I will also include a remark concerning this distribution-specific aspect.
>
> For ActiveTcl and the core in general, we actually plan to introduce a
> TIP that removes the case-sensitivity of package names. It is fairly
> useless in practice, and has confused many users of various
> extensions.
I disagree to this plan.
All identifiers are case sensitive until now in Tcl AFAIK, variables,
functions, dict keys, array indices, namespaces. In my opinion also
package names are "identifiers" - these can't be "useless" until the
complete language is changed to case-insensitive.
Removing case-sensitivity removes potentiality, I don't see any reason
for that.
I remember of the terrible inconsequences in PHP, variable names case
sensitive, functions and namespaces are case insensitive, etc.
What are the drawbacks of case sensitivity?
--
Gerhard Reithofer
Tech-EDV Support Forum - http://support.tech-edv.co.at
MartinLemburg@Siemens-PLM
bwidget, than it won't collide with the current naming of the original
BWidget's. But is this really wanted?
IMO it's worth thinking of changing the package names to be
caseinsensitive, because names of packages would be easier unique.
And ... changing the package naming conventions/system is not about
questioning the whole tcl casesensitivityness!
I agree, that something like in PHP is really awful, but this
suggestion is not about to change the syntax of tcl, nor its
semantics. It's only about changing the way to access external
functionality via packages/modules in a more unique and easier way.
But that's only my opinion/expectation.
Best regards,
Martin
On Nov 11, 10:45 pm, Gerhard Reithofer <gerhard.reitho...@tech-
Gerhard Reithofer
On Wed, 12 Nov 2008, MartinLemburg@Siemens-PLM wrote:
> So to say ... if someone wants to build a widget package and calls it
> bwidget, than it won't collide with the current naming of the original
> BWidget's. But is this really wanted?
Yes.
Example: if an application has a function called MainInit, why shouldn't
I create and use mainInit within the same "package", this could also
apply to package names.
No doubt that it may be better to use namespaces, then even my init
function could be named MainInit and the risk for confusion would be
smaller.
> IMO it's worth thinking of changing the package names to be
> caseinsensitive, because names of packages would be easier unique.
That applies to all aspects of a programming language, functions,
variables, namespaces...
> And ... changing the package naming conventions/system is not about
> questioning the whole tcl casesensitivityness!
> I agree, that something like in PHP is really awful, but this
> suggestion is not about to change the syntax of tcl, nor its
> semantics. It's only about changing the way to access external
> functionality via packages/modules in a more unique and easier way.
I haven't found a reason which justifies implementing case-sensitivity
for package names (ecxcept the comments obove). Further I haven't found
any aspect in tcl which does not respect case-sensitivity.
Or am I wrong?
> But that's only my opinion/expectation.
But that's only my opinion/expectation :-)))
What I would like are suggestions or "best practices" for using case in
programming.