Re: version conflict for package "Tcl": TCL_VERSION vs TCL_PATCH_LEVEL
- From: Donald G Porter <dgp@xxxxxxxx>
- Date: Wed, 30 Apr 2008 10:14:29 -0400
Olaf Dietrich wrote:
Okay, so _without_ stubs, you recommend to use
Tcl_InitStubs(interp, TCL_VERSION, 1);
(works with all patchlevels of the MAJ.MIN version)
and _with_ stubs:
Tcl_InitStubs(interp, TCL_VERSION, 0);
No, I recommend the latter in both cases.
However, you were rejecting that. You were explicitly asking for a
formulation that would enforce a "no future minor release" constraint,
so I gave you the answer you were asking for.
--
| Don Porter Mathematical and Computational Sciences Division |
| donald.porter@xxxxxxxx Information Technology Laboratory |
| http://math.nist.gov/~DPorter/ NIST |
|______________________________________________________________________|
.
- Follow-Ups:
- Re: version conflict for package "Tcl": TCL_VERSION vs TCL_PATCH_LEVEL
- From: Olaf Dietrich
- Re: version conflict for package "Tcl": TCL_VERSION vs TCL_PATCH_LEVEL
- References:
- version conflict for package "Tcl": TCL_VERSION vs TCL_PATCH_LEVEL
- From: Olaf Dietrich
- Re: version conflict for package "Tcl": TCL_VERSION vs TCL_PATCH_LEVEL
- From: Donald G Porter
- Re: version conflict for package "Tcl": TCL_VERSION vs TCL_PATCH_LEVEL
- From: Olaf Dietrich
- version conflict for package "Tcl": TCL_VERSION vs TCL_PATCH_LEVEL
- Prev by Date: Re: How to parse this plz tell me!!!
- Next by Date: Re: version conflict for package "Tcl": TCL_VERSION vs TCL_PATCH_LEVEL
- Previous by thread: Re: version conflict for package "Tcl": TCL_VERSION vs TCL_PATCH_LEVEL
- Next by thread: Re: version conflict for package "Tcl": TCL_VERSION vs TCL_PATCH_LEVEL
- Index(es):