summaryrefslogtreecommitdiffstats
path: root/unix/tclUnixFile.c
diff options
context:
space:
mode:
authorpooryorick <com.digitalsmarties@pooryorick.com>2023-02-28 11:42:15 (GMT)
committerpooryorick <com.digitalsmarties@pooryorick.com>2023-02-28 11:42:15 (GMT)
commitbb2f06fc739eb91a9f1499fbfbc4fa346172660e (patch)
treea56e7f124ddae3a10f98aea31db92da5bc336d07 /unix/tclUnixFile.c
parent5d8ae9bf171d1047032458977316799f24130a48 (diff)
downloadtcl-bb2f06fc739eb91a9f1499fbfbc4fa346172660e.zip
tcl-bb2f06fc739eb91a9f1499fbfbc4fa346172660e.tar.gz
tcl-bb2f06fc739eb91a9f1499fbfbc4fa346172660e.tar.bz2
Reverted [d156af9fb76dd2f4] and removed tests io-52.20 io-75.6 io-75.7, as this
commit, intended to fix issue [b8f575aa2398b0e4], breaks the semantics of [read] and [gets]. Such a change would require an accepted TIP. See [b8f575aa2398b0e4] for further discussion. jn: @pouryorick See [b8f575aa2398b0e4] for the reason why this commit is not appropriate: It gets core-8-branch back in the buggy state it was, without even providing a real solution everyone agrees on. You shouldn't revert my patch just because I reverted yours. pooryorick: As I explained, the reason for this reversion is that it hard-codes an unapproved change in the semantics of [read] and [gets] into the test suite. Jan, your statement that it's a "revenge" reversion is false. I spent a month trying to find some alternative to this reversion before actually performing it. A commit that codifes in its tests changes in semantcs to [read]/[gets] simply shouldn't be on core-8-branch.
Diffstat (limited to 'unix/tclUnixFile.c')
0 files changed, 0 insertions, 0 deletions