Re: [Plplot-devel] xwin.c is now split

[Vince D. <vi...@sa...>]

>>>
Come on! the tk driver needs the plframe, that needs the xwin driver! 

And yes, I think that plframe.o should be part of the driver, and as 
such linked with tk.o to make tk_drv. But the plframe only makes sense 
with tclAPI, so should we link them all? No, if I configure with 
--enable-tcl --disable-tk, than tclAPI.o will be built, plframe.o will 
not, and I can use other driver then the tk_drv one.
>>>

To throw in my 2 cents... I agree very much with the above.  The plframe
and tk.c are both parts of the tk driver.  The fact one may be able to
link one or other without the other is beside the point, and this means
that the stuff which was in xwin.c is required by the tk driver (again
whether one can link or not without it). The various
'plwidget.tcl' and related files are also effectively part of the tk
driver (even though they aren't compiled, of cours).

However, the 'pure-tcl' bindings (tclAPI.c) can be used completely
independently (and in fact much of that code isn't even used by the tk
driver --- one might wish to split that out into a common 'Plbasic_Init'
used by Tcl AND tk bindings, and the 'Pltcl_Init' stuff whicvh is only
used by the Tcl bindings (not Tk).

cheers,

-- Vince

<http://www.santafe.edu/~vince>