Tcl

Documentation would need to be beefed up before use to include the
definition (and description of manner of use) of the types referred to.

See also Bug #414930

Logged In: YES
user_id=75003

I have retrieved manpage and sample code from the specified
urls and attached them to this report.

Logged In: YES
user_id=585068

The manual page is here (it's mostly complete):
http://www.xmission.com/~georgeps/implementation/software/tcl/Resolver.3

It was tested with this man.macros from Tcl 8.5:
http://www.xmission.com/~georgeps/implementation/software/tcl/man.macros

Here is my sample resolver code (it could be extended):
http://www.xmission.com/~georgeps/implementation/software/tcl/resolver.c

Logged In: YES
user_id=75003

George, feel free to attach the manpage here. Even if the
code goes away such docs should help to make the
determination if the api is wanted or not. Internal notes
are of interest as well, IMHO.

Logged In: YES
user_id=79902

This API mistake has been festering since 8.0; there's no
hurry to fix it. Indeed, if it slipped 8.5 I wouldn't worry
at all.

The problem is: is the interface this function and its
friends expose the interface that we would like to expose?
Is it something that perhaps we expose and deprecate? (I
don't have answers; just questions.)

Logged In: YES
user_id=585068

I wrote most of a manual page for this, but I was told in
the Tcler's Chat that this resolver code would probably be
replaced. If anyone wants the manual page let me know. I
based it on comments in the resolver code and my own little
test program that created a custom resolver.

Logged In: YES
user_id=80530

Re-opened. Either Tcl_AddInterpResolvers() should be
private and has an incorrect name, or it should be
public, and we should convert this bug report into a
Feature Request to make that happen.