diff options
| author | Jim Meyering <jim@meyering.net> | 2000-03-04 07:57:35 +0000 |
|---|---|---|
| committer | Jim Meyering <jim@meyering.net> | 2000-03-04 07:57:35 +0000 |
| commit | 634dad84ba2f42a82a9e5d40bcd4af135b00e0c4 (patch) | |
| tree | 44bc4bd0a6a489a23f7a3429715ee3806d0734bc /lib | |
| parent | 871812bcec61d6126ed62b1f8214a909b09e2f34 (diff) | |
| download | coreutils-634dad84ba2f42a82a9e5d40bcd4af135b00e0c4.tar.xz | |
Add Bruno's comment justifying use of volatile.
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/localcharset.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/lib/localcharset.c b/lib/localcharset.c index 86f43b588..461320823 100644 --- a/lib/localcharset.c +++ b/lib/localcharset.c @@ -48,6 +48,12 @@ char *xmalloc (); char *xrealloc (); +/* The following static variable is declared 'volatile' to avoid a + possible multithread problem in the function get_charset_aliases. If we + are running in a threaded environment, and if two threads initialize + 'charset_aliases' simultaneously, both will produce the same value, + and everything will be ok if the two assignments to 'charset_aliases' + are atomic. But I don't know what will happen if the two assignments mix. */ /* Pointer to the contents of the charset.alias file, if it has already been read, else NULL. Its format is: ALIAS_1 '\0' CANONICAL_1 '\0' ... ALIAS_n '\0' CANONICAL_n '\0' '\0' */ |