From: Andreas K. <and...@ac...> - 2012-12-06 21:40:42
|
On Thu, Dec 6, 2012 at 1:32 PM, Brian Griffin <bri...@me...> wrote: > On Dec 6, 2012, at 1:00 PM, Andreas Kupries wrote: > >> On Thu, Dec 6, 2012 at 12:35 PM, Donald G Porter <don...@ni...> wrote: >>> >>>>> This is Revision 3 of the Tcl 9 Wart Removal List. >>> >>> * [info library] >>> Or remove $::tcl_library. But don't keep both. >> >> +1 on removing the variable, keeping the command. > > If the variable is removed, then how does it get set? > I would remove the command, otherwise add an optional argument to set the value, although that would be odd. AFAIK this is set in C code at tclsh startup and initialization. Setting it is AFAIK not exposed. Although I have to admit I have no idea what happens should 'set tcl_library something'. This is something I have never tried. Is that actually supported and working? >> ... Doable, via file in the platform directory with a fixed name, >> either for the shlib itself (i.e. fixed extension regardless of >> platform), or a file holding the name of the platform shlib ... Right >> now I am tending to make the shlib fixed-name/extension. > > Looking at the filesystem to find a file to figure out what the extension should be is expensive! Please don't do that if you don't have too. (stat+nfs==bad) Yes, which is why my thinking goes to making the generated extension fixed, regardless of which platform-specific directory the critcl generated shlib will end up in. -- Andreas Kupries Senior Tcl Developer Code to Cloud: Smarter, Safer, Faster™ P: 778.786.1122 F: 778.786.1133 and...@ac... http://www.activestate.com Learn about Stackato for Private PaaS: http://www.activestate.com/stackato Tcl'2013, Sep 23-27, New Orleans, LA, USA. |