On 2013-10-28 21:44-0500 Maurice LeBrun wrote:

> On Monday, October 28, 2013 at 14:44:48 (-0700) Alan W. Irwin writes:
> > On 2013-10-28 14:23-0700 Alan W. Irwin wrote:
> >
> > > The goal here is to make it easy for the user to choose between
> > > using either version 3 of [incr Tcl_tk] or version 4.  In fact, my
> > > testing of those two cases is being held up because I don't have
> > > an easy way to switch between them (without a lot of code editing).
> > > So some quick help on how to make this possible would be appreciated.
> >
> > Soon after I sent the above appeal off, I discovered how our build
> > system set the macro TCL_DIR and how bindings/tcl/tclMain.c used that
> > macro to help determine the Tcl global variable $dir. Therefore, I
> > will try something similar to globally set itcl_package_name, etc.,
> > (unless you guys can think of a better method).
>
> I think in order to avoid coding in package version dependencies where none
> should exist, make sure your desired tcl package library directories are all
> properly positioned in auto_path.  E.g. on my Kubuntu 12.04.3 box:
>
> $ tclsh8.4
> % puts $auto_path
> /usr/share/tcltk/tcl8.4 /usr/lib /usr/local/lib/tcltk /usr/local/share/tcltk 
> /usr/lib/tcltk /usr/share/tcltk
>
> $ tclsh8.5
> % puts $auto_path
> /usr/share/tcltk/tcl8.5 /usr/lib /usr/local/lib/tcltk /usr/local/share/tcltk 
> /usr/lib/tcltk /usr/share/tcltk
>
> That first entry enables it to find the right packages.

Hi Maurice,

First, I think version 4 of itcl... is the wave of the future.  The
reason I say that is itcl version 4 is already completely integrated
with Tcl-8.6 and built on top of its inherent low-level OO
capabilities of that version of Tcl. (This is the first time itcl has
ever been integrated with Tcl.) Furthermore, version 4 of itk and
iwidgets are built on top of that integrated version of itcl-4.
Second, some web comments I read imply that although version 3 of
itcl... is legacy code, that code still should work fine with
Tcl/Tk-8.6. So what I plan to do is build both version 3 and version 4
of itcl... as part of the Tcl/Tk-8.6 installation directory tree that
is provided by build_projects, and use the method I outlined before to
allow the user to choose one or the other of those versions in a
consistent way.  I emphasize that convenience method should be viewed
as preliminary (since I am not much of a Tcl/Tk expert), and if
someone can come up with a better method in our scripts of making that
choice, that is fine with me.

Once that preliminary method of choosing version 3 or version 4 of
itcl... for Tcl/Tk8.6 is implemented, then we will be in a position to
test how compatible our PLplot scripts are at a fundamental level with
those two versions. I expect from previus experience with version 3
that our scripts will be fine with that version, but my preliminary
tests indicate our scripts will have to be modified (more than just
the package require commands) to get them to work with version 4 of
itcl....  (More on that later once I marshall all the evidence.)

Once our scripts work properly with both itcl.... version 3 and
itcl... version 4 we may want to remove all this version choice for
itcl... and simply demand that itcl... version 3 can only be used if
it is installed in a Tcl/Tk8.5 directory tree while itcl... version 4
can only be used when it is installed in a Tcl/Tk8.6 directory tree.
But we can cross that bridge when we come to it.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to