It's not that the word "island" has any particular significance; it's that all names starting with "is" followed by a lowercase letter are reserved (in external linkage and in the global scope of files that #include <ctype.h>), so that future versions of the language can add more standard library functions along the lines of isalpha, isdigit, etc., without making the current standards committee guess in advance which specific names following that pattern their successors might want to add in the future, and without breaking existing code. (Unless that existing code ignores these rules, which seems to be fairly common in practice.)
isisland(x);
Or to know if an element is a member of a particular terror group (or an Egyptian goddess): isisis(y); isisisland(z);
In this case you'd typically then construct a memory fence.Naturally, this would imply the validity of the optimization:
x = toilet(y); -> if (!isilet(y)) x = toilet(y);
[1] https://www.open-std.org/jtc1/sc22/WG14/www/docs/n2625.pdf (I hope that’s the right version)
Yes, that means that an implementation will warn you that your code might break in the future, but on the day when it actually breaks, it will just stop complaining. Why they could not just mandate detecting invalid uses of reserved identifiers is beyond me.
> Each header declares or defines all identifiers listed in its associated subclause, and optionally declares or defines identifiers listed in its associated future library directions subclause and identifiers which are always reserved either for any use or for use as file scope identifiers.
> Function names that begin with str and a lowercase letter may be added to the declarations in the <stdlib.h> header.
Or 7.31.13:
> Function names that begin with str, mem, or wcs and a lowercase letter may be added to the declarations in the <string.h> header.
So according to the standard, if your code #includes string.h, it may conflict with a future version of the standard if you use names like "strong" or "memorize". This is extraordinarily unlikely, though.
OK, I know it's only an offhand remark in a blog post, but now I'm going to have to spend significant energy on:
1. Finding where these identifiers are reserved, exactly, because obvious sources like https://pubs.opengroup.org/onlinepubs/9699919799/functions/V... don't seem to include them?
2. Trying to come up with the intended usage for these identifiers (`island` I imagine, might be a scope: only accessible to other identifiers on the same island? oh my...)