Re: [tcltk-perl] Why is Tcl a subclass of Tck::Tk?

[Gisle A. <gi...@Ac...>]

"Jeff Hobbs" <je...@Ac...> writes:

> I'd like to actually remove some of the Tcl API crap that I
> think has been around for eons (all the Get|SetVar*, Append*).
> These things do truly expose some Tcl C APIs (all the old
> string-only ones), but to what purpose?

I agree with that.  API functions like that could also just move to
different namespace to get them out of the way.  I think it would be
valuable to actually have the Tcl namespace "empty".  All I think it
should have is a AUTOLOAD that turns all method calls into a tcl
procedure call.  I.e. that:

    $tcl->foo($a, $b)

is always the same as

    $tcl->call("foo", $a, $b)

is now.  That has the potential of simpilifying the Tk stuff I think.

For the Tcl::Tk stuff I would really like to be able to move all that
deals with perlTk compatiblity to its own module.  The API to trigger
it could be the same, but as this grows in complexity you don't want
to load it when all you need is to use the Tk interface as it is.

--Gisle