Re: naming of base interpreters

Virden, Larry W. wrote:

> Originally when tclkits were released, there was a push for developers
> to rename variations they created when the functionality inside  
> changed -
> people who wanted to add new extensions, etc. were strongly encouraged
> not to call the result tclkits so that there was no confusion about
> what one would and would not see.
>
> Is this still a goal? If so, is there a web page stating this policy
> in a form that could be forwarded along to projects to let them  
> know the
> requirement?
>
> Also, will this also apply to what has, to date, been called tclkit  
> lite?

Yes, this is still important.  Perhaps even more than before.  Good  
point.

I am calling the new tclkits based on tclkit lite "tclkit-cli",  
"tclkit-dyn", and "tclkit-gui".  I have also always called earlier  
versions of Tclkit Lite "tclkitlite" or some such, *never* plain  
"tclkit".

There may come a day when a tclkit-lite based version of Tclkit  
becomes more important than the existing large crop of tclkit  
platform builds, but that's not the case today.

So for now, if it has Mk4tcl and IncrTcl in it (or fully emulates  
them), and nothing else (other than what is essential to run tclkit,  
i.e. tcl/tk/tclvfs and pwb/rechan) then I think it is fine to call  
the executable "tclkit".  Otherwise, we should continue to pick a  
different name.  Hey, here's your chance to be creative! <wink>

FWIW, I do intend to build a new generation of tclkits at some point,  
using the new tclkit lite core and adding the Mk4tcl and IncrTcl  
extensions in VFS as *dynamic* extensions (at least for the big-three  
platforms) - or as very good emulations.  It all depends on how the  
OO-to-end-all-OOs and the Vlerq-to-end-all-Metakits projects progress...

Note that you can easily wrap starkits up so they launch something  
other than "tclkit" by using the "-interp name" option in sdx wrap  
(see "sdx help wrap").

-jcw

PS.  Have not "burned" this into a web-page policy, this post should  
end up in the mailing list archives though.