diff options
author | jan.nijtmans <nijtmans@users.sourceforge.net> | 2022-09-10 21:10:20 (GMT) |
---|---|---|
committer | jan.nijtmans <nijtmans@users.sourceforge.net> | 2022-09-10 21:10:20 (GMT) |
commit | f6715923b8e582240ab916b3a1432af4cc1ecc56 (patch) | |
tree | 4617af91a260fbcc070645aac13b188a945e2515 /macosx/README | |
parent | 6b3ace837fc82f4c7474d30636b0b7ecf8aa4e44 (diff) | |
download | tk-f6715923b8e582240ab916b3a1432af4cc1ecc56.zip tk-f6715923b8e582240ab916b3a1432af4cc1ecc56.tar.gz tk-f6715923b8e582240ab916b3a1432af4cc1ecc56.tar.bz2 |
Fix [006403a25d]: various comment/documentation fixes
Diffstat (limited to 'macosx/README')
-rw-r--r-- | macosx/README | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/macosx/README b/macosx/README index 4ed334f..db51db2 100644 --- a/macosx/README +++ b/macosx/README @@ -548,7 +548,7 @@ appropriate place to drain the main NSAutoreleasePool and replace it with a new pool. This is done by calling the method [NSApp _resetAutoreleasePool], where _resetAutoreleasePool is a method which we define for the subclass. Unfortunately, by itself this is not -sufficient for safe memory managememt because, as was made painfully +sufficient for safe memory management because, as was made painfully evident with the release of OS X 10.13, it is possible for calls to TclDoOneEvent, and hence to CheckProc, to be nested. Draining the autorelease pool in a nested call leads to crashes as objects in use |