TclX commands

[Damon Courtney <da...@your.unreality.com>]

Ok,

    I am currently writing up a TclX compatibility library.  Of course,
I can't write the whole thing, nor do I want to.  I'm just writing up the
basic commands that I think are really important (and mostly easy to do).

    My question is this.  Should I include these commands as commands of
Rivet?  Or, should I include these commands in a package called Tclxcompat?
Currently, I have them in a package called Tclxcompat, but I think it might
be cool to have them as commands of Rivet.

    The major reason being, if the user has TclX installed and required,
the commands will never get sourced.  Commands of Rivet only get sourced
when they're required and they don't already exist.  So, a user types:

lassign $list foo boo

    And they get it.  If TclX is loaded, they get it because TclX has the
command.  If TclX is not loaded, they get it because Rivet will pick it
up and give it to them.

    Any thoughts?

D

Re: TclX commands

["David N. Welton" <da...@dedasys.com>]

Damon Courtney <da...@your.unreality.com> writes:

> > Why not just use TclX if you want TclX?  Or is this more of a
> > TclX-light, with the commands you find most useful?

>     This is just a Tcl-only library of commands that I find most
> useful.  I love TclX.  I'll always install it on my server, but
> there are those out there who aren't really compiler masters.  Those
> people may not ever make the leap to compile and install TclX with
> their server.  But, I think they should have some of these commands.

Unfortunately, this is a Tcl problem, something that needs to be
solved at a higher level.  If we can contribute, though, that would be
great.  Tcl + C is such a powerful combination, it is extremely
unfortunate that packages produced in this way can't be made available
in a standard way from a standard site.  The activestate guys are
working on this, in theory.

-- 
David N. Welton
   Consulting: http://www.dedasys.com/
Free Software: http://people.debian.org/~davidw/
   Apache Tcl: http://tcl.apache.org/
     Personal: http://www.efn.org/~davidw/

Re: TclX commands

[Damon Courtney <da...@your.unreality.com>]

> Why not just use TclX if you want TclX?  Or is this more of a
> TclX-light, with the commands you find most useful?

    This is just a Tcl-only library of commands that I find most
useful.  I love TclX.  I'll always install it on my server, but there
are those out there who aren't really compiler masters.  Those people
may not ever make the leap to compile and install TclX with their
server.  But, I think they should have some of these commands.

> This sounds like non-Tcl core kinds of things that could go in their
> own package.  Sure they would be cool commands as part of Rivet, but
> that doesn't mean everyone wants or needs them.
> 
> Once we put something in the core, I don't think it is going to be
> possible to take it out again, at least not without pissing people
> off.

    I agree.  I'll just leave it as a package.

D

Re: TclX commands

["David N. Welton" <da...@dedasys.com>]

Damon Courtney <da...@your.unreality.com> writes:

>     I am currently writing up a TclX compatibility library.  Of
> course, I can't write the whole thing, nor do I want to.  I'm just
> writing up the basic commands that I think are really important (and
> mostly easy to do).
 
Why not just use TclX if you want TclX?  Or is this more of a
TclX-light, with the commands you find most useful?

>     My question is this.  Should I include these commands as
> commands of Rivet?  Or, should I include these commands in a package
> called Tclxcompat?  Currently, I have them in a package called
> Tclxcompat, but I think it might be cool to have them as commands of
> Rivet.

This sounds like non-Tcl core kinds of things that could go in their
own package.  Sure they would be cool commands as part of Rivet, but
that doesn't mean everyone wants or needs them.

Once we put something in the core, I don't think it is going to be
possible to take it out again, at least not without pissing people
off.

-- 
David N. Welton
   Consulting: http://www.dedasys.com/
Free Software: http://people.debian.org/~davidw/
   Apache Tcl: http://tcl.apache.org/
     Personal: http://www.efn.org/~davidw/