From: John Ousterhout <ouster@aj...> - 2000-10-30 00:46:07
At 07:41 PM 10/27/2000 +0800, Mark Harrison wrote:
>John Ousterhout <ouster@...> wrote:
> > My
> > understanding is that its sources would become inseparable from
> > the Tcl core sources like tclInterp.c; no one would ever compile
> > one without the other.
>Correct, but it would go into a shared library for people concerned
>about memory, etc. Total reactionaries can stand by with the "rm"
Following the line of discussion of the last couple of days, I'd
argue that [incr Tcl] should not go in a separate library. It should
just become part of the core. In fact, [incr Tcl] as a name, concept,
and implementation would cease to exist at this point. What we would
have instead is just the "Tcl class facilities ", or, just "Tcl"
("of course Tcl has object-oriented programming: duh!"). This is
similar to other things that have been added to Tcl and Tk: we have
"Tcl's I/O facilities", not the "TclX file commands", even though the
original file facilities came from TclX.
This is a big enough change that I'd argue for making the release
Tcl 9.0, even though it doesn't introduce any compatibility problems.
The change in major release number would catch people's attention and
help to publicize the [incr Tcl] inclusion. By the way, Tcl 8.0
didn't introduce any significant compatibility problems but we still
changed the major version number to highlight the new facilities.
John Ousterhout 650-210-0102 tel
Chairman and Chief Technology Officer 650-230-4070 fax
Ajuba Solutions ouster@...
The TclCore mailing list is sponsored by Ajuba Solutions
To unsubscribe: email tclcore-request@... with the
word UNSUBSCRIBE as the subject.