1. Forum
  2. Usenet
  3. COMP.LANG.TCL

  • Re: Tcl/Tk 8.6.14 RELEASED

    From Andreas Leitgeb@21:1/5 to Brian Griffin on Sun Mar 3 14:30:07 2024
    Brian Griffin <[email protected]> wrote:
    The Tcl Core Team is pleased to announce the 8.6.14 releases of the Tcl dynamic language and the Tk toolkit. This is the fourteenth patch release
    of Tcl/Tk 8.6. More details can be found below.

    Thanks to all contributors!

    * Harmonize handling of ~ in paths across platforms.
    *** POTENTIAL INCOMPATIBILITY ***

    I recall some discussion about this changing in 9.0, didn't
    think that stuff was meant to change in 8.6, but may have
    missed discussions of truely change-worthy details.

    Some quick tests with a freshly compiled 8.6.14 (on linux) didn't show
    any surprises against my known previous state for "~something" as
    literal name for "cd", "open", or "file join" or "glob".

    What changes would I need to check for?

    My scripts often need to handle "~/..." and "~user/..." read from
    config files, and if anything changes within 8.6, I want to be prepared.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Porter@21:1/5 to All on Mon Mar 4 12:28:11 2024
    * Harmonize handling of ~ in paths across platforms.
    *** POTENTIAL INCOMPATIBILITY ***

    I recall some discussion about this changing in 9.0, didn't
    think that stuff was meant to change in 8.6, but may have
    missed discussions of truely change-worthy details.
    What changes would I need to check for?

    Two different sets of changes.

    In Tcl 9, TIP 602 approved ending all interpretation of ~ in pathnames.
    BIG change.

    The note accompanying Tcl 8.6.14 refers to Ticket 9c5a00c69d

    https://core.tcl-lang.org/tcl/tktview/9c5a00c69d

    An earlier bug fix had the unwanted side effect of making ~ expansion
    on Windows no longer conform to the documentation. This misbehavior
    is present in releases 8.6.9 through 8.6.13.

    Tcl 8.6.14 corrects this misbehavior, but it's been around so long, an incompatibilty warning was attached in case anybody got used to it.

    --
    | Don Porter Applied and Computational Mathematics Division |
    | [email protected] Information Technology Laboratory |
    | http://math.nist.gov/~DPorter/ NIST | |______________________________________________________________________|

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Leitgeb@21:1/5 to Don Porter on Mon Mar 4 23:41:45 2024
    Thanks a lot for clarification!

    Don Porter <[email protected]> wrote:

    * Harmonize handling of ~ in paths across platforms.
    *** POTENTIAL INCOMPATIBILITY ***

    I recall some discussion about this changing in 9.0, didn't
    think that stuff was meant to change in 8.6, but may have
    missed discussions of truely change-worthy details.
    What changes would I need to check for?

    Two different sets of changes.

    In Tcl 9, TIP 602 approved ending all interpretation of ~ in pathnames.
    BIG change.

    The note accompanying Tcl 8.6.14 refers to Ticket 9c5a00c69d

    https://core.tcl-lang.org/tcl/tktview/9c5a00c69d

    An earlier bug fix had the unwanted side effect of making ~ expansion
    on Windows no longer conform to the documentation. This misbehavior
    is present in releases 8.6.9 through 8.6.13.

    Tcl 8.6.14 corrects this misbehavior, but it's been around so long, an incompatibilty warning was attached in case anybody got used to it.


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)