diff options
author | Karl Berry <karl@freefriends.org> | 2021-08-31 08:30:42 -0700 |
---|---|---|
committer | Karl Berry <karl@freefriends.org> | 2021-08-31 08:30:42 -0700 |
commit | a4e28bb23a248e8c3c6fc5df6a64ffca16a6cad1 (patch) | |
tree | a0dbcddc0ef966e8f00fe74fe0863ae9b1341340 | |
parent | ceb9bdd1dc3b82b7381b783947abd067110723ed (diff) | |
download | gnulib-a4e28bb23a248e8c3c6fc5df6a64ffca16a6cad1.tar.gz |
autoupdate
-rw-r--r-- | lib/idx.h | 20 |
1 files changed, 0 insertions, 20 deletions
@@ -56,26 +56,6 @@ * Because 'size_t' is an unsigned type, and a signed type is better. See above. - Why not use 'ssize_t'? - - * 'ptrdiff_t' is more portable; it is standardized by ISO C - whereas 'ssize_t' is standardized only by POSIX. - - * 'ssize_t' is not required to be as wide as 'size_t', and some - now-obsolete POSIX platforms had 'size_t' wider than 'ssize_t'. - - * Conversely, some now-obsolete platforms had 'ptrdiff_t' wider - than 'size_t', which can be a win and conforms to POSIX. - - Won't this cause a problem with objects larger than PTRDIFF_MAX? - - * Typical modern or large platforms do not allocate such objects, - so this is not much of a problem in practice; for example, you - can safely write 'idx_t len = strlen (s);'. To port to older - small platforms where allocations larger than PTRDIFF_MAX could - in theory be a problem, you can use Gnulib's ialloc module, or - functions like ximalloc in Gnulib's xalloc module. - Why not use 'ptrdiff_t' directly? * Maintainability: When reading and modifying code, it helps to know that |