Re: [TCLCORE] CFV WARNING: TIP #414: Add (back) Tcl_InitSubsystems as Public API

[Griffin, B. <bri...@me...>]

On Mar 29, 2013, at 8:49 AM, "Porter, Don" <don...@ni...>
 wrote:

> 
> ________________________________________
> From: Jan Nijtmans [jan...@gm...]
>> ..If Tcl_InitSubsystems() is exposed, then
>> Tcl_SetInitialEncodings() and TclpFindExecutable() should
>> be exposed as well, ...
> 
> The function of TclpSetInitialEncodings() has been
> exposed since TIP 258 went Final, in all Tcl releases 8.5.0
> and later.
> 
> With that, and a public Tcl_InitSubsystems() the fine-grained
> ability to call T_FE part by part would be done.  (It might be
> nice to offer a public form of TclpFindExecutable() as well,
> but not necessary, since the other two parts can be
> harmlessly called multiple times.)

Ideally, non-Windows platforms would have an equivalent to GetModuleFileName and it wouldn't be necessary to "Find" the executable, it would just "know".  Linux has /proc/self/exe, what about other systems?

Beyond the req's here, I would love to see a C API equivalent to [auto_execok]!

But I digress... Sorry.

> 
> When it comes to solving the problem of offering more controlled
> access to the set of functions that Tcl_FindExecutable() currently
> performs, the essential missing piece is is a public Tcl_InitSubsytems().
> Get that, and that task is done.

+1 

> 
> A completely different task of giving the Tcl startup sequence a
> complete reinvention and rewrite might well be worth doing.  And
> the initsubsystems* branches may be pointing in good directions
> to accomplish that.  But it's not the task I'm seeking TIP 414 to
> accomplish, and frankly, it's not a project I'm comfortable taking
> on targeting its first appearance in a stable patch release.

+1 

-Brian